Draft a PR description from the diff in Copilot Chat
GitHub Copilot Chat on a pull request writes a description from the diff: summary, test plan, and residual risk.
A PR body you can edit once: what changed, how to verify it, and what could still break.
- 1
Open Copilot Chat on the PR
Run this after the diff is stable. Regenerate if you force-push a different story.
- 2
Edit the test plan against your machine
Run at least one checklist item yourself. Copilot guesses commands when the diff is silent.
- 3
Paste into the description field
Replace the empty template, not the conversation. Keep the risk section honest for production paths.
The prompt to paste
You are on this pull request. Read the full diff and any existing title. Write a PR description for reviewers who did not author it. Return markdown with these sections: ## Summary Two short paragraphs max: user-visible behavior change, then why (bug, feature, refactor, dependency). ## Test plan Checklist of concrete steps a reviewer can run. Include commands where the repo has them. Mark anything you cannot infer from the diff as "[confirm]". ## Risk One paragraph: blast radius, migrations, feature flags, or "none apparent." Name files or endpoints that deserve extra eyes. ## Out of scope Bullets for changes you see in the diff that are unrelated to the stated goal, or write "none." Rules: - Do not claim tests were added unless the diff shows them. - Do not paste marketing language or praise. - If the diff is huge, prioritize the top five files by behavior impact.
A polished description is not a review. Copilot can miss security-sensitive diffs in generated or config files.
Sample case written by Hidden Logic Lab. Not affiliated with GitHub Copilot.
More in Coding
Get new cases in your inbox
Weekly notes on new use cases and agent workflows. No product pitches.