pr-creator

Write PR descriptions like a developer posting in Slack, not like an AI summarizing a diff.

IS: creating the GitHub PR (or updating an existing one's title and body): a short human-sounding description, a Linear ID title prefix, commit restructuring, and reviewer guidance for large diffs.
IS NOT: reviewing the diff for bugs (use pr-reviewer), watching CI and review comments after creation (use pr-babysitter), or cutting npm releases (use autoship).

Reference Files

File	Read When
`references/pr-polish.md`	Commit history is noisy (fixup, WIP, or "address review" commits), the diff exceeds 500 lines, or the user asks to polish, tidy, restructure, or split the PR

Copy this checklist and work through it: