PR Description Generator
Most PR descriptions say "fixes the thing" and make the reviewer reverse-engineer the rest. Fill in the four things reviewers actually look for (what, why, how it was tested, what breaks) and get a clean Markdown description that gets your PR reviewed faster. Runs entirely in your browser.
This PR has breaking changes
## Summary _What this PR does and why, in two or three sentences._ ## Changes - _List the concrete changes, one per line._ ## Type of change - [x] Feature ## Testing - [ ] Unit tests added or updated - [ ] Manual verification (describe what you clicked through) ## Breaking changes None. ## Reviewer notes _Anything that makes review faster: risky areas, files to read first, screenshots for UI changes._
What should a pull request description contain?
Five things, in this order: a summary the reviewer can absorb in 20 seconds, the concrete list of changes, the type of change, how it was tested, and an explicit breaking-changes statement (including "None", silence reads as "didn't check"). Link the issue so the PR closes it on merge. The generator above produces exactly that structure; the PR description skill gives Claude the same structure so it can draft from your diff inside your editor.
Why not just let the commits speak?
Commits record what changed line by line; they rarely record why, what was tested, or what a deployer needs to know. Reviewers approve faster, and with better comments, when the description answers those three questions up front. Two minutes of writing here routinely saves a day of review round-trips.