skills.rest
vstorm-co
vstorm-coOFFICIAL
Explore all skills by this author →
WebsiteGitHub

Pull request review

Reviews pull request diffs against repository conventions in a maintainer's order.

49|11|Updated Jul 31, 2026
Search Tags:#git#testing#code review#pull request#conventions#diff#defect detection
One-click install
npx skills add https://github.com/vstorm-co/agenticos --skill pull-request-review-vstorm-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Pull request review
Source: https://github.com/vstorm-co/agenticos/tree/main/backend/app/core/catalog/skill_gallery/software/pull-request-review
Command: npx skills add https://github.com/vstorm-co/agenticos --skill pull-request-review-vstorm-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews often miss real defects because reviewers focus on the diff itself rather than what the change assumes, or they block on style instead of substance. This Skill structures the review so bugs, failure paths, and missing tests are caught before opinions are voiced. ## Core Features & Use Cases - Ordered review checklist: Walks through claim verification, failure paths, tests, conventions, and blast radius in the sequence a maintainer follows. - Calibrated feedback: Distinguishes confirmed bugs with reproducing inputs from subjective style preferences, so authors know what must change. - Sibling call-site sweep: When a change touches one of several similar call sites, it checks the others for the same defect. - Use Case: A teammate opens a PR modifying a shared utility. Use this Skill to verify the description matches the diff, confirm a test fails without the fix, and check every other caller of the utility before approving. ## Quick Start Review the current pull request diff against this repository's conventions and report bugs, missing tests, and affected call sites.

Frequently Asked Questions about Pull request review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a pull request effectively?▼

Read the surrounding code before the diff, then verify the change does what it claims, check failure paths like errors and concurrency, confirm tests fail without the fix, follow repository conventions, and assess what else calls the changed code.

What should I check first in a code review?▼

First verify the diff does what the description claims, since mismatches between intent and implementation are the most common problem. Then examine failure paths such as errors, empty results, concurrency, and partial writes.

How to tell if a pull request test is meaningful?▼

A meaningful test fails on the old code without the fix. If a test passes both before and after the change, it tests nothing and provides no protection against the defect being addressed.

When should I not block a pull request?▼

Do not block on style issues that a formatter should own, and do not approve a diff you did not understand just because the author is senior. Block only on verified bugs and convention violations.

Why check sibling call sites during code review?▼

When a change touches one of several similar call sites, the same defect usually exists in all of them. Sweeping the siblings catches the full blast radius instead of fixing only the instance that happened to be modified.

Related Skills

Explore More Software Engineering Skills→
segersnielssegersniels

Review PR

Analyze pull request diffs to generate prioritized feedback on bugs, style, and security.

Community
Intermediate
p-o-ke-naep-o-ke-nae

github-flow

Guide GitHub Flow branching, commits, testing, pull requests, and squash merges.

Community
Intermediate
criniscrinis
4

css-review

Reviews CSS code for redundancy, duplication, and semantic consistency with linters.

Community
Advanced
RyderFreeman4LogosRyderFreeman4Logos
12

code-review

Automate GitHub PR reviews with scale-adaptive direct or delegated review.

Community
Advanced