Git Commit Message Generation

Generate a commit message from the actual staged changes (git diff --cached). The message must let a reader know "what changed and why" without opening the diff.

Workflow

1. Look at the changes: run git status --short and git diff --cached --stat to confirm there is something staged. If the staging area is empty, stop and ask the user — never invent a commit message out of nothing.
2. Pick a type: choose exactly one type prefix based on the changes (if one commit mixes types, ask the user to split it):
   • feat: new feature
   • fix: bug fix
   • docs: documentation only
   • refactor: refactor (behavior unchanged)
   • test: add or change tests
   • chore: build, dependencies, misc
3. Write the subject: format type: English imperative phrase, ≤50 characters. Start with a verb: "Add…", "Fix…", "Remove…", "Unify…". Ban empty subjects like "update code", "some changes", "fix bug".
4. Write the body (optional but recommended): 1–3 lines explaining why, not a play-by-play of how. Bug fixes must state the trigger conditions; features should describe the user-visible change.
5. Output: give a ready-to-run command, not bare text the user has to assemble.

Rules