Conventional Commits Generator
Write commit messages from the actual diff.
Format
type(scope): short summary
Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert.
Process
- Read the diff. Group unrelated changes; recommend split commits if needed.
- Choose type from behavior, not from file type alone.
- Summary: imperative, 72 chars or fewer, no period, says why-level change not "update file".
- Body only if the why is not obvious. Footer for BREAKING CHANGE and issue refs.
Output
- Recommended message(s)
- If the diff should be split, the split plan
- What not to include (secrets, generated noise)
Rules
- Do not invent ticket numbers.
- Do not write "misc fixes" or "update stuff".