PR Writer

Create or refresh PRs with reviewer-facing titles and bodies. The body is a cover note, not a changelog, template, validation log, or file-by-file summary.

Output Priorities

1. Match the full branch diff against the base branch, not the latest commit or stale PR text.
2. Describe the shape and effect of the change before implementation detail.
3. Explain why, risk, tradeoff, migration, or review focus only when useful.
4. Use the smallest structure that makes review easier.
5. Omit routine validation, unverified issue refs, customer data, PII, placeholders, and tool traces.

Plain-Language Pass

Before creating or updating the PR, reread the title and body as a reviewer.