Regitize

Regitize Commit Messages

Rewrite commit messages without changing committed file trees or merge topology. Never push rewritten history.

Workflow

1. Locate this skill directory so its bundled scripts can be executed by absolute path.
2. Verify the repository and target branch. Default to the current local branch. Refuse a detached HEAD unless the user names a local branch.
3. Inspect context with git status --short, git branch --show-current, and git log --graph --decorate --oneline --all.
4. Run node <skill-dir>/scripts/collect-history.mjs --output <repo-git-dir>/regitize/history.json. Read the entire generated history, including every patch. For an unusually large history, process it in batches but do not skip commits.
5. Derive one proposed message per commit:
   • Use an imperative subject, normally no more than 72 characters.
   • Describe the behavioral or architectural outcome, not file operations.
   • Add a body only for important rationale, constraints, migrations, or secondary effects supported by the diff.
   • For merge commits, describe what was integrated; use parent context because the merge diff may be empty.
   • Do not invent intent, issue numbers, or impact absent from the repository evidence.
   • Preserve a message that is already the most accurate concise description.
6. Write a plan matching references/plan-format.md to <repo-git-dir>/regitize/message-plan.json.
7. Run node <skill-dir>/scripts/rewrite-history.mjs --plan <plan-path> without --apply. Fix every validation error.
8. Show the user the branch, commit count, signed-commit warning if any, and a complete table of old short SHA, old subject, and proposed subject. Explain that all descendant SHAs will change.
9. Stop and obtain explicit approval for the displayed plan. Approval of an earlier or partial plan does not count.
10. After approval only, run the same command with --apply. If signed commits exist, also set acknowledgeSignatureLoss: true in the plan only after the user explicitly accepts signature loss.
11. Verify the new log and report the old head, new head, and backup ref printed by the script. Do not force-push unless the user separately asks for it.

Safety rules

• Rewrite one local branch per invocation. Other branches and tags remain at their existing SHAs.
• Do not combine this task with squashing, reordering, content edits, author changes, or date changes.
• Do not bypass expectedHead; regenerate the plan if the branch moved.
• Treat published/shared history as high risk. Recommend coordinating with collaborators before any push.
• The helper preserves snapshots and parent topology, creates a backup ref, and refuses unsupported commit metadata unless explicitly acknowledged.

Resources

• scripts/collect-history.mjs captures commit metadata, stats, and full textual patches.
• scripts/rewrite-history.mjs validates and applies an approved plan using Git plumbing.
• references/plan-format.md defines the plan schema and recovery commands.