Pull request description prompt for ChatGPT or Claude

Run it in your repository, or paste a diff. In this prompt version you paste the text yourself. The steps are under "How to use it" below.

Works in ChatGPT, Claude, Gemini or any chatbot. Get your diff with git diff main...HEAD (use your base branch) and paste it where marked. For very large diffs, paste git diff --stat plus the files that matter most.

Write the pull request text from the diff below. Use only what the diff and my notes show.

Why this change (if you know): [reason, ticket link, or "not sure"]
Tests I ran (if any): [or "none yet"]
Diff: [paste here]

Output, ready to paste:
- Title: under 70 characters, imperative.
- Summary: 2 to 4 sentences, what and why. If the reason is not in my notes, write "Why: not stated" instead of guessing.
- Changes: bullets grouped by purpose, naming the files. Separate behaviour changes from refactors, renames, formatting and generated files.
- Risk and review focus: where to look hard and why. Call out breaking changes, migrations, new env vars, dependency changes, auth code touched, deleted code, and logic changed with no tests.
- How it was tested: only what I told you or what the diff shows. Never claim tests passed. If unknown, write "Not stated" and give a suggested test plan.
- Rollout and rollback: only if a migration, flag, config or deploy step is involved.
- Questions a reviewer is likely to ask: up to 5, tied to a specific hunk, with your best answer or "Needs author input".
- Needs your input: the facts you could not get from the diff.

Rules: do not invent a motivation, ticket number, benchmark or test result. Do not describe changes you did not see. Plain short sentences, no hype words, no emojis, no em dashes.

Before: A commit-list dump: "fix res.send / bump qs / bump proxy-addr / bump morgan"

After (skill output, from a real test run): Test run on four real commits from a public web framework. Output, unedited: "Title: Preserve ETag with Transfer-Encoding in res.send; bump deps". It grouped the fix and the three dependency bumps separately, noted which bumps were runtime vs dev, said the diff showed no lockfile change, wrote "Why: not stated in the diff", and caught that the branch it was asked to diff against was behind another branch.

• It only knows the diff and commit messages. The reason for the change comes from you.
• It does not run tests. "How it was tested" says Not stated unless you tell it.
• It does not open the PR. You paste the text.
• Very large diffs: it reads the stat first and then the key files, and says what it skipped.

PR Description and Review Prep is also a skill you install once and call in plain words, so you do not paste the prompt each time. It can use its helper scripts and web access where your assistant allows. See the skill page, or read how to install skills.

See every skill for developers.