Write a pull request description
A PR description reviewers love: what, why, how to test, and risks.
The prompt
Write a pull request description.
Diff or summary of changes: [PASTE `git diff` or describe]
Related ticket/issue: [LINK or ID]
Why this change: [REASON]
Format:
- Title — imperative, specific.
- Summary — what changed and why (2–4 sentences).
- Changes — bullet list grouped by area.
- How to test — numbered steps and expected results.
- Screenshots/recordings — placeholder if UI changed.
- Risks and rollout — migration, feature flags, backward compatibility.
- Checklist — tests added, docs updated, no secrets committed.
Describe only what's in the diff; flag anything that looks unintentional.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Software Development prompts
What to fill in
- PASTE `git diff` or describe
- LINK or ID
- REASON
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Refactor code to be cleaner and easier to maintainImproves structure, naming, and design without changing behavior.
- Convert code to another language or frameworkIdiomatic translation of code between languages or frameworks, with notes on differences.
- Write unit tests for my codeComprehensive unit tests covering happy paths, edge cases, and failures.
- Write a clear, reproducible bug reportBug reports developers can act on immediately — steps, expected vs. actual, environment, and evidence.