pr-issue
PR & Issue
Write the title and body Vim-style — area: summary, then labelled sections
in template order.
Three words carry this skill. Symptom: every body opens with the thing a human noticed. Mechanism: the next paragraph names the exact code that misbehaves. Receipts: any output shown was really produced, never output that would plausibly have been produced — and a change to rendered output shows that output.
A PR is read once, in a hurry, by someone deciding whether to approve. An issue is read once, weeks later, by someone deciding whether to work on it — and again by whoever picks it up. Both readers are cold: switching in from other work, often not the author, often new to this corner of the codebase. Every sentence earns its place by moving that decision along.