Agent skill
git-rename-branch
{{ ƔƔƔ }} Rename branch if needed
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/git-rename-branch
SKILL.md
Assess and Rename Current Branch
- If user has specified a new name, apply it; otheriwse, get the current branch name with
git branch --show-current - Get a summary of what's actually been done on this branch:
git log main..HEAD --onelineto see commitsgit diff main..HEAD --name-onlyto see changed files
- Compare the branch name against the actual changes:
- Does the name still accurately describe the work?
- Is the scope broader or narrower than the name implies?
- Does the name follow the
<prefix>/<short-description>convention?
- If the name is still accurate, say so and stop
- If a rename is warranted, suggest a better name and explain why
- Format:
<prefix>/<short-description>— all lowercase, hyphens, imperative mood (add-featurenotadds-featureoradding-feature)
- Format:
- Await approval — if accepted:
- Rename locally:
git branch -m <new-name> - Rename on remote:
git push origin HEAD:<new-name>thengit push origin --delete <old-name> - Set upstream:
git branch --set-upstream-to=origin/<new-name>
- Rename locally:
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?