review-pr

Run parallel multi-perspective reviews on GitHub pull requests.

6|2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/i-standard1/yamasaki --skill review-pr-i-standard1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/i-standard1/yamasaki/tree/main/.claude/skills/review-pr
Command: npx skills add https://github.com/i-standard1/yamasaki --skill review-pr-i-standard1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR reviews are often slow and inconsistent across multiple quality axes. This skill automates parallel, multi-perspective reviews to accelerate identifying issues in pull requests.

Core Features & Use Cases

  • Parallel, multi-agent PR review across security, code quality, architecture, domain logic, and tests.
  • Consolidated verdict with actionable feedback and suggested fixes.
  • Works with GitHub PRs by number, URL, or the current branch's PR, suitable for large-scale PRs.

Quick Start

Invoke the PR review process by issuing /review-pr to analyze the target PR.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I automate GitHub PR reviews for code quality and security?

Automate GitHub PR reviews by running parallel, multi-perspective AI assessments that evaluate security, code quality, architecture, domain logic, and tests to return a consolidated report with actionable fixes.

What is the best way to review large-scale pull requests quickly?

Reviewing large-scale pull requests quickly is achievable by deploying parallel, multi-agent reviews that analyze five distinct quality axes simultaneously, consolidating the feedback into a single actionable verdict.

How do I run a code review on a current branch's GitHub pull request?

Run a code review on a current branch's GitHub pull request by invoking the review process, which automatically targets the active PR using five specialist agents to identify issues across architecture and logic.

Do I need API keys to automate multi-perspective PR reviews?

No API keys are required to automate multi-perspective PR reviews. The process integrates results from five specialist agents and returns a consolidated report directly without needing external authentication setup.

What aspects of a pull request are evaluated during an automated code review?

During an automated code review, the pull request is evaluated across five dimensions: security vulnerabilities, general code quality, architectural alignment, domain logic accuracy, and the correctness of associated tests.

Can I review a GitHub pull request by URL or number?

Yes, you can review a GitHub pull request by providing its specific PR number, the full URL, or by targeting the PR associated with your current working branch, ensuring flexible integration into existing workflows.