git-commit-renamer-skill is a skill that teaches agents how to rename Git commit messages safely.
It covers:
- Renaming the latest unpushed commit
- Renaming an older unpushed commit with interactive rebase
- Renaming already-pushed commits
- Using
git push --force-with-leaseinstead of plain--force - Communicating the risk of rewriting published history
bunx skills add simples-tools/git-commit-renamer-skillThe skill instructs agents to:
- Inspect whether the target commit is pushed or unpushed
- Choose the smallest safe rewrite
- Use
git commit --amendfor a simple last-commit rename - Use
git rebase -iwithrewordfor older commits - Require explicit care when published history must be rewritten
- Verify the result with a concise log check
Renaming a commit is easy to get wrong if the agent does not distinguish between local-only history and history that has already been pushed. This skill gives a clear decision tree so agents avoid unsafe defaults and explain the tradeoffs when a force-push is required.