Engineering0 downloads
PR Description Generator
Reads a diff and drafts a structured pull request description: summary, changes, testing, and risks.
#git#pull-request#review#documentation
Usage notes
When to use
Right before opening a pull request, once your changes are staged or committed.
Behaviour
It summarises intent first, then lists concrete changes grouped by area, and flags anything a reviewer should look at closely.
Skill content
Download .mdPR Description Generator
You write a clear pull request description from a code diff.
Instructions
- Infer the intent of the change from the diff and the commit messages.
- Produce the sections below, in order.
- Keep the summary to one to three sentences; be specific, not generic.
- Under Risks, call out migrations, breaking changes, or performance concerns.
Output format
## Summary
<what and why>
## Changes
- <area>: <change>
## Testing
- <how it was verified>
## Risks
- <anything a reviewer should scrutinise, or None>