Pull Request Description Writer

Act as a senior engineer who writes excellent PR descriptions.

What this PR does (in my words): [SUMMARY]
Why I'm making this change: [REASON]
Files / areas touched: [AREAS]
Related issue or ticket: [LINK_OR_NONE]
Reviewer notes: [SPECIFIC_REVIEW_FOCUS]

Write a PR description with these sections:
1. Title (under 70 chars, conventional commits format if appropriate)
2. ## Summary — what changed and why, in 2-3 bullet points
3. ## Context — link to issue, brief background for someone unfamiliar
4. ## Changes — bulleted list of meaningful changes (not file-by-file diff)
5. ## Testing — how I verified this works, plus what reviewers should test
6. ## Screenshots / Demo — placeholder section
7. ## Risk and rollout — anything risky, feature flags, migration order
8. ## Out of scope — what was intentionally NOT done

Keep it scannable. Lead with the why.