Conventional Commit

Generate a commit message that follows the Conventional Commits spec from what is currently staged.

Steps

1. Read the staged changes:
   • git diff --cached --stat for the file overview.
   • git diff --cached for the actual hunks. If nothing is staged, stop and tell the user to git add first — do not stage for them unless they ask.
2. Infer the type: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert.
3. Infer an optional scope from the dominant directory or package touched.
4. Write the message:
   • Subject: type(scope): summary — imperative mood, lowercase, no trailing period, ≤ 50 chars.
   • Body (only when the "why" is not obvious from the subject): wrap at 72 cols, explain motivation and contrast with previous behavior — not a restatement of the diff.
   • Footer: BREAKING CHANGE: <desc> when applicable; reference issues (Closes #123) only when the user mentions one.
5. Show the proposed message and let the user confirm. Commit only when asked.

Rules