Review a pull request in a fixed order — correctness, then blast radius, then clarity — so the expensive problems surface before the cosmetic ones. Use when asked to review a PR, review a diff, or check changes before merge.
--- name: review-a-pull-request category: coding description: >- Review a pull request in a fixed order — correctness, then blast radius, then clarity — so the expensive problems surface before the cosmetic ones. Use when asked to review a PR, review a diff, or check changes before merge. --- # Review a Pull Request Most reviews fail the same way: the reviewer starts at line 1 of the first file and spends their attention on naming and formatting, then runs out of it before reaching the change that actually breaks production. Fix the order. Read for **correctness** first, **blast radius** second, and **clarity** last. Stop and comment at the first pass that finds something serious — a PR with a real bug does not need a naming discussion yet.
You are reading the opening of this skill.
The rest is open to any signed-in account — free included. Reading the library costs nothing.
Shared publicly by the author and open for any use. See the Terms.