review-pull-request

Reviews GitHub pull requests end-to-end using the gh CLI with severity-leveled feedback.

3|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/ruskicoder/system-prompts --skill review-pull-request-ruskicoder
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-pull-request
Source: https://github.com/ruskicoder/system-prompts/tree/main/prompt-orchestrator/.opencode/skills/review-pull-request
Command: npx skills add https://github.com/ruskicoder/system-prompts --skill review-pull-request-ruskicoder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing pull requests thoroughly is time-consuming and inconsistent: reviewers miss CI failures, skip commit history, give vague feedback, or rubber-stamp large diffs. This Skill provides a structured, repeatable procedure for conducting complete PR reviews with the GitHub CLI. ## Core Features & Use Cases - Context and Scope Assessment: Fetches PR metadata, commit history, and CI check status via gh pr view and gh pr checks, then sizes the review effort based on files and lines changed. - Systematic Diff Analysis: Walks through gh pr diff output evaluating correctness, edge cases, error handling, security, performance, readability, and test coverage. - Severity-Leveled Feedback: Classifies every comment as Blocking, Suggestion, Nit, or Praise, then submits a formal review with gh pr review --approve, --request-changes, or --comment. - Use Case: A reviewer assigned a 20-file PR runs the workflow to inspect commits one by one, flags a null-pointer risk as Blocking with a suggested code fix, and submits a request-changes review with precise file and line references. ## Quick Start Ask the AI to review pull request number 42 in the current repository, checking CI status and classifying all findings by severity before submitting the review.

Frequently Asked Questions about review-pull-request

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

FAQPage Schema
How do I review a GitHub pull request from the command line?▼

Use the GitHub CLI: run gh pr view to fetch metadata, gh pr diff to inspect changes, gh pr checks to verify CI status, and gh pr review with --approve, --request-changes, or --comment to submit your formal review.

How to review a large pull request with many changed files?▼

For PRs over 15 files or 500 lines, review commit by commit using gh pr diff --patch and prioritize critical code paths. For PRs over 30 files, flag the PR for potential decomposition and focus on security and data boundaries.

What should I check when reviewing a pull request diff?▼

Evaluate seven dimensions: correctness against the PR description, edge cases like nulls and race conditions, error handling, security risks such as injection or secret leakage, performance issues like N+1 queries, naming readability, and test coverage.

Does gh pr review require special permissions or setup?▼

Yes, the GitHub CLI must be authenticated with repository read and write access, which you can verify with gh auth status. Git must also be available for local commands like git log and git diff when local verification is needed.

What are common pull request review mistakes to avoid?▼

Avoid rubber-stamping without reading diffs, flooding reviews with trivial nits while missing logic bugs, demanding unrelated refactors outside the PR scope, and giving vague criticism without explaining the problem or proposing an alternative.