Rewrite Commit Messages

Safely rewrite existing git commit messages using git filter-repo.

Use this skill when the user wants to:

• rename one or more historical commit messages
• normalize repeated generated messages
• replace noisy tranche/merge wording with cleaner summaries
• perform a message-only history rewrite with explicit mappings

Do not use this skill for:

• squashing or reordering commits
• changing file contents
• partial staging or creating a new commit from the working tree

Use /commit for new commits and /squash-commits for rebase-based history cleanup.

Safety model

This skill rewrites commit SHAs. Treat it as history surgery.

Before making any change:

1. Record and print the full original HEAD SHA.
2. Confirm the working tree is clean.
3. Create a backup ref/tag pointing at the original HEAD.
4. Require explicit old→new message mappings.
5. Prefer rewriting only commit messages; do not modify trees, authors, or dates unless the user explicitly asks.