PR Description from a Diff

Prompt template

Write a pull-request description from this diff:

{{diff}}

Intent (one line, what the author was trying to do): {{intent}}

Output as markdown with these sections:

## Why
Two short paragraphs. Lead with the problem this solves or the behavior it changes; only then mention the technical approach. Skip filler like 'This PR introduces…'.

## What changed
Bulleted, one bullet per file or coherent change. Each bullet is one sentence written so a code-reviewer can skip the diff and still know what to look at.

## How to verify
Numbered steps a reviewer can execute. Use exact commands / URLs / inputs. No 'should work' hand-waving.

## Risk
One sentence: what's the worst thing that could go wrong, and what would the user see? Include if there's a rollback / feature-flag.

Tone: terse, technical, no emoji.

Curator notes

The 'how to verify' section is the one most authors skip. Forcing exact commands here makes the reviewer's job 90% easier.