review-pr

Fetch pull request diffs via GitHub CLI and analyze code by severity.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/bswrundquist/devtools --skill review-pr-bswrundquist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/bswrundquist/devtools/tree/main/src/devtools/templates/claude/user/.claude/skills/review-pr
Command: npx skills add https://github.com/bswrundquist/devtools --skill review-pr-bswrundquist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of conducting thorough and structured code reviews for pull requests, ensuring code quality, security, and maintainability.

Core Features & Use Cases

  • Automated PR Analysis: Fetches PR details and diffs using gh CLI.
  • Systematic Review: Evaluates code across correctness, security, performance, design, testing, and operational aspects.
  • Structured Feedback: Delivers findings organized by severity (Must Fix, Should Fix, Nitpicks) with a summary assessment.
  • Use Case: When a developer submits a pull request, invoke this Skill to get a detailed, actionable review report, speeding up the feedback loop and improving code quality.

Quick Start

Use the review-pr skill to review pull request number 123.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I automate a structured code review for a GitHub pull request?

Automated code review fetches pull request details and diffs via the GitHub CLI to evaluate correctness, security, performance, design, testing, and operational concerns, delivering structured feedback organized by severity.

Do I need the GitHub CLI installed to review pull requests?

Yes, the GitHub CLI (`gh`) is required. The code review process depends on the `gh` command-line tool to fetch pull request metadata and diffs directly from your repository.

What aspects of code quality are checked during a pull request review?

Code quality checks during a pull request review cover correctness, security vulnerabilities, performance bottlenecks, software design, testing coverage, and operational concerns to ensure maintainability.

How is pull request feedback organized after an automated review?

Pull request feedback is organized by severity levels: Must Fix, Should Fix, and Nitpicks. The structured review also includes a summary assessment to help prioritize actionable code improvements.

Can I analyze specific pull request numbers for security and performance issues?

Yes, you can target a specific pull request number to analyze its diffs for security vulnerabilities and performance issues, providing a detailed and actionable review report for that exact PR.

What is the best way to speed up the developer feedback loop for code quality?

Invoking an automated structured code review upon pull request submission speeds up the feedback loop by systematically assessing code quality, security, and design without manual inspection overhead.