writing-pr-bodies
Installation
SKILL.md
Writing PR bodies
A PR body is read by three people who did not watch the work: the engineering lead, the reviewer
who merges, and the person who tells the client what shipped. Write for all three at once.
The shape is fixed; fill pr-body-template.md section by section and save it as
PR-BODY-<issue>.md next to the brief. The coordinator opens the PR with --body-file.
The two parts, in this order
## What changes for the team— 3–6 sentences the client's operations manager can read. What the operator sees differently, what stays exactly the same, what could go wrong and how we would notice. Name screens and fields by the app's own labels (messages/ar.json), never file names, never table names, never an acronym. Copy the brief's paragraph and correct it only where the code ended up different — say so if it did. Never head this section "In plain English".## What changed in the code— one bullet per file or decision, each saying why, not just what. Name the seam (which existing function the new code plugs into), the one derivation for any money/holdings fact, and every decision the brief reserved and who made it.