Goal
Write a commit message and pull request description that tell a reviewer what changed, why, and how to check it.
Inputs
- Diff or list of changed files: [paste the diff or a summary of changes]
- Why the change was made: [the problem or request behind it]
- How it was tested: [manual steps, automated tests, or none yet]
- Team convention: [conventional commits, plain imperative, other]
- Linked issue, optional: [issue reference]
Output format
- Commit message:
- Subject line under 72 characters, imperative mood
- Blank line
- Body wrapped at 72 characters: what changed and why, not how
- Pull request description with these headings:
- Summary: two or three sentences
- Changes: bullet list grouped by area
- Testing: numbered steps a reviewer can follow
- Risks and rollback: what could break and how to undo it
- Screenshots: a placeholder line if the change affects UI
- Split suggestion: if the diff mixes unrelated changes, propose how to split it into separate commits.
Check before answering
- The subject describes the outcome, such as "Fix duplicate charge on retry", not "Update files".
- No claims of testing that the inputs do not mention.
- Every changed area in the diff appears under Changes.
- No secrets, internal hostnames or personal names copied from the diff into the message.
- Breaking changes are stated at the top of the description.
- The tone is factual; no filler such as "small tweaks".
- The convention given is followed exactly, including type prefixes if used.






