#commit message generator

Git Commit Message & PR Description from Diff

Turn a diff and intent into Conventional Commits, a full PR body, test plan, and reviewer notes. Flags risk without inventing files.

Act as a staff engineer writing the commit and PR that a reviewer can trust. Use the diff as source of truth. Do not invent files, tests, or behavior that are not in the diff or the stated intent. Inputs: - Diff: [Paste git diff or gh pr diff] - Intent: [What I meant to do] - Repo conventions: [Conventional Commits / Jira keys / none] - Ticket: [ID or none] - Risk I worry about: [Risk] - Reviewer audience: [Team, new hire, open source] - Tests I ran: [Commands and results, or none] - Breaking?: [Yes / No / Unsure] Generate: 1. Diff readout: What actually changed, in 8-12 bullets. Group by file. Call out anything that does not match Intent. 2. Commit message options (3): Conventional Commits unless conventions say otherwise. Subject 50-72 chars. Body: why, not a file list. Mark recommended. If the diff is two unrelated concerns, split into 2 commit messages and say so. 3. PR title (60 chars or less) and full PR body in this markdown: - Summary - Motivation - Changes - Test plan (checkboxes). Include Tests I ran. Add missing tests as unchecked boxes, labeled "not run / not in diff" - Risks and rollback - Screenshots: only if UI; else "n/a" 4. Reviewer guide: 4 places to look first. One question you want them to answer. 5. Risk flags: race conditions, access control, migrations, feature flags, secrets. Only if the diff supports it. If Risk I worry about is not visible in the diff, say so. 6. Follow-ups: 3 items that should not sneak into this PR. Constraints: - Never invent a test, screenshot, or benchmark. - Do not claim fully covered if Tests I ran is none. - Subjects: imperative mood, no period, no WIP unless Intent says so. - If Diff is thin or truncated, list what you cannot certify. - No "please find attached."