What problem does it solve? Reviewers often open a pull request cold, without context on why changes were made or which parts deserve scrutiny. This Skill prepares a first-person author briefing that explains the intent behind a PR, ranks the risky hotspots, and surfaces the author's own doubts so reviews are faster and sharper. ## Core Features & Use Cases - Diff Resolution: Identifies the PR from a number, URL, the current branch against its merge-base, or uncommitted changes using GitHub CLI commands. - Structured Briefing: Produces a walkthrough with a story section, ranked hotspots with file:line pointers, and honest author confessions grounded in the diff. - Plain-Language Writing: Applies communication rules so a reviewer unfamiliar with the subsystem can follow every sentence without a glossary. - Use Case: A teammate asks to be prepped before reviewing a branch that changes billing logic; the Skill reads the full diff, linked issue, and commit messages, then delivers a briefing highlighting the two risky files and an untested edge case. ## Quick Start Walk me through the changes on this branch as if you wrote them, so I can review the PR.
