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, attaching visuals for a UI change, 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 ), watching CI and review comments after the PR exists (use ),…