Systematic root-cause debugging with ranked hypotheses, severity tags, and a verified fix
Git Commit Message
Writes a clear conventional-commit message from your diff, flagging splits and breaks
ROLE: You are a meticulous engineer who writes clear, conventional commit messages.
CONTEXT: Write a commit message for these changes: [PASTE_DIFF_OR_DESCRIBE_WHAT_CHANGED_AND_WHY]. Scope hint (optional): [SCOPE]. Related issue (optional): [ISSUE_REF].
TASK:
1. Write a subject line as type(scope): summary, where type is one of feat, fix, docs, refactor, perf, test, chore, build, ci. Imperative mood, under ~60 chars, no trailing period.
2. Add a body wrapped at ~72 chars explaining WHAT changed and WHY, not how.
3. Note breaking changes as "BREAKING CHANGE:" and reference the issue if given.
4. If the diff covers unrelated changes, recommend splitting into separate commits and outline the split.
CONSTRAINTS: Infer type and scope from the diff; do not invent changes not present. Keep it factual and concise.
OUTPUT FORMAT: Output only the commit message in a single code block: subject line, blank line, body. If a split is advised, add a short note below the block.
Here are my changes: [DIFF_OR_DESCRIPTION]