Skill Rename
Renames a skill’s slug everywhere — filename, frontmatter name, internal references, per-project overrides.
Entry verified April 21, 2026
The short answer
When a skill’s name stops matching what it does, rename it everywhere at once. This skill grep-finds every reference (across ~/.claude/, project .claude/ dirs, and skill documentation), updates them, and flags any that look ambiguous.
When to use it
You wrote /commit-and-push, then dropped the “and-push” behaviour, and the name’s now a lie. Or you built /qa and realised /audit fits better.
Setup
- 1
Save as ~/.claude/commands/skill-rename.md. Argument: old-slug new-slug.
- 2
Skill runs: mv the .md file, update frontmatter name, grep for old-slug across ~/.claude/ and current project, update references, warn if old-slug appears in README or external docs.
- 3
Always reports what it changed — does not silently rewrite shared docs.
Example
You: /skill-rename commit-and-push commit
Claude: Renamed commands/commit-and-push.md → commands/commit.md
Updated frontmatter name: “commit”
Updated 3 internal refs (commit-and-push → commit) in commands/qa.md, rules/git-workflow.md, CLAUDE.md
⚠️ README.md mentions /commit-and-push — update manually or add alias.Source & attribution
- Author
- Bryan Collins
- Licence
- MIT (author's own work)
- Type
- Original
Original pattern published under MIT — attribution preserved by convention, not licence requirement.
Caveats
If the skill is published publicly, issue a README note with the old slug as a redirect — don’t silently break other people’s muscle memory.
56 skills across 10 categories, all licence-verified.