pr-creator

Write PR descriptions like a developer posting in Slack, not an AI summarizing a diff. The reviewer has none of your context, so the body answers what the diff cannot: why, what it costs if wrong, and where you want their view. The diff answers what changed.

IS: creating or updating a GitHub PR's title, body, draft state, and reviewers, plus the commit restructuring and review path that make a large diff readable.
IS NOT: changing the code in the diff or reviewing it for bugs (use tidy), watching CI and review comments after the PR exists (use pr-babysitter), or cutting npm releases (use autoship).

Reference Files

File	Read When
`references/pr-polish.md`	Commits contain fixup, WIP, or "address review" noise, the diff exceeds 500 lines, or the user asks to polish, restructure, squash, or split the PR

Workflow

Copy this checklist to track progress: