Pre-fetched context
!git status --short
!git diff --stat
Instructions
Commit changes quickly. Do not summarize after — move on immediately.
- •Run
git diffandgit log --oneline -5 - •Group unrelated changes into separate commits if needed
- •For each commit:
git add <files>→git diff --cached --stat→ commit - •Message: Conventional Commits (
type(scope): description), English, imperative, under 72 chars. Match repo style if one exists.- •Add a body that briefly explains why the change was made and any relevant background. Keep it concise — just enough for a future reader to understand the motivation without re-reading the diff.
- •Omit the body only when the subject line alone is self-explanatory (e.g., fixing a typo).
- •Ask user ONLY if: changes span many unrelated concerns with unclear grouping, possible secrets, or generated files that shouldn't be committed.