pr-recap
PR recap
Write one recap of a pull request for the people who review it. A reviewer should understand from the first screen why the change exists, what it changes, and how. The recap points into the diff. It does not replace reading the diff.
Run this workflow locally. The recap is one PR comment: GitHub Markdown plus one PNG uploaded to the PR's own host. It needs gh, and for the sketch, Bun and the bundled sketch tool. It posts nothing to any other host.
Decide whether the PR gets a recap
Skip the recap when the diff has no behavior that a reviewer must trace. Examples are a version pin and its hashes, a typo or wording fix, a formatting-only change, a lockfile-only change, and the revert of one commit. A version pin skips even across a major version, because a pin has no mechanism to sketch.
For a skipped PR, post nothing on GitHub. Put one line in your reply:
Recap skipped for PR <n>: <what the diff is>, <why it needs no recap>.
Otherwise, write the recap. Write it again after each push that changes the diff, once the new head is published and any gate run on it has reached its outcome.