PromptDev
Write a pull request description
Turn your change notes into the PR description reviewers actually want: what changed, why now, how it's tested, and what to look at hardest.
Last updated
Fill in the blanks
Assembled in your browser — nothing you type is stored or sent anywhere.
Your prompt
Write a pull request description from my notes below.
Structure: a one-line summary a changelog could reuse; **Why** (the problem, and why now); **What changed** (grouped by area, not file-by-file); **How it's tested** (only what I actually did — never claim tests I didn't mention); **Review notes** (the risky part a reviewer should stare at, and anything I chose NOT to do, with the reason). Keep it under 250 words, no marketing tone. If my notes leave a section empty, write "—" rather than padding it.
My notes:
switched invoice PDF from html2canvas to pdf-lib. bundle -800kb. tested manually with 3 invoices incl. unicode names. didn't touch the preview path — still old renderer. watch the font embedding fallback.
Model-agnostic — works in Claude, ChatGPT, Gemini or any AI chat.
Why this prompt works
- →"Why" before "what" mirrors how reviewers read — a diff they can see; the reason for it they can't.
- →The never-claim-untested-things rule matters specifically here: a generated "all tests pass" line in a PR is a small lie with a long audit trail.
- →Asking for the not-done list turns scope cuts from surprises-in-review into decisions-on-record.