Write a Pull Request Description From a Diff
Turn a branch's changes into a reviewer-friendly PR description — what changed, why, and how to test it.
0 likes
0 dislikes
Sign in to rate this prompt
Prompt
Write a pull request description for the change below.
Diff (or a summary of the commits and changes):
{{diff}}
Context (optional — the issue it addresses, why now): {{context}}
Structure it as:
- **Summary** — what this PR does, in one or two sentences.
- **Why** — the motivation or problem it solves.
- **What changed** — the key changes as a short bulleted list (grouped if it touches several areas).
- **How to test** — concrete steps or commands a reviewer can run to verify it.
- **Risks / notes** — anything a reviewer should watch for (migrations, breaking changes, follow-ups).
Keep it scannable and honest — describe what the diff actually does, and flag anything that looks unrelated or risky rather than glossing over it. Omit a section if the change genuinely doesn't need it.
Why this prompt works
-
How to Deploy an AI Agent
Every deployment problem follows from one property: you don't know how long a run takes, because you didn't write the path. Why the run m...
Read the guide → -
MCP Authorization and OAuth
Optional until you opt in, then very specific. Why the resource parameter is mandatory even when the server ignores it, why PKCE doesn't ...
Read the guide → -
MCP Transports: stdio vs Streamable HTTP
There are two transports now, not three, and the one that vanished is the one most tutorials still document. What each is exposed to, why...
Read the guide →