Write a pull request description from a diff
Turns a raw diff into a PR description a reviewer can use: what changed, why, and what to check. It does not restate the diff line by line.
AI Place Hub
45
Write a pull request description for the diff below.
Sections, in this order:
Summary - two sentences, what changed and why, no implementation detail.
Changes - a short bullet list of what actually changed, grouped by file or area, not line by line.
Testing - how this was verified, or what a reviewer should check if it was not.
Risk - anything that could break, or "none identified" if genuinely nothing stands out.
Do not describe the diff mechanically. If the reason for a change is not evident from the diff, say the reason is unclear rather than inventing one.
--- diff ---
{{diff}}Fill these in
Type your values and Copy gives you the finished prompt, not the template.
Nothing filled in yet - Copy will give you the template with placeholders.
Notes from the author
People skip writing the risk section by hand, and reviewers read it first. Make the model name a risk or say that it found none, and it cannot quietly leave the section out.
For information only, not professional advice. You use it at your own risk and we are not liable for any loss or damage. See the disclaimer.
Tagged