Git Commit Assistant

Quick start

• Review staged changes and ensure they cover a single concern.
• Choose <type>(optional-scope) and write an imperative 50-72 character summary.
• Add body for why/decisions/trade-offs; footers for breaking changes or issue references.
• Show the message in a fenced code block, ask for approval to commit, then commit only if approved.
• See references/commit_rules.md for full rules and examples.

Workflow

1. Inspect changes

   • Check git status and git diff --cached to confirm what will be committed.
   • If changes mix concerns or include formatting noise, ask to split or stage appropriately.

2. Select type/scope

   • Allowed types: feat, fix, refactor, docs, test, chore, build, ci, perf, style.
   • Scope is optional; keep it short (e.g., api, auth, deps).