PR write

Write concise, reviewable PR titles and bodies. Explain what shipped and why it matters for review. No essays.

When to use

• User asks to write, draft, update, improve, or review a PR title, body, or description.
• User says "create PR", "open PR", "PR body", "PR summary", "squash message", "describe my changes".
• Changes need before/after visuals, benchmark tables, mermaid diagrams, or usage snippets.

Don't use for commit messages, changelogs, release notes, or issue triage. Keep PR scope only.

Title rules

• One line, under 72 chars when possible.
• Imperative, specific, no fluff. Name the change, not the effort.
• Good: add cursor pagination to list_runs
• Bad: some fixes and improvements to various stuff
• No prefixes unless repo uses them. Match base branch convention.