review-pr

Orchestrate parallel reviewer agents to assess GitHub PR diffs across multiple dimensions.

8|Updated Nov 4, 2016
One-click install
npx skills add https://github.com/coil398/dotfiles --skill review-pr-coil398
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/coil398/dotfiles/tree/main/.claude/skills/review-pr
Command: npx skills add https://github.com/coil398/dotfiles --skill review-pr-coil398

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews PR diffs by orchestrating hybrid reviewer agents to provide structured, multi-perspective feedback on code changes.

Core Features & Use Cases

  • Parallel reviewer roles (correctness, consistency, quality, security, architecture) to accelerate feedback.
  • Diff-driven analysis that reads RUN_DIR/diff.patch and outputs per-role reports to RUN_DIR/review-01-<ROLE>.md.
  • Orchestrated workflow where the main Claude coordinates agents and aggregates verdicts for user-friendly results.

Quick Start

Provide a PR identifier, branch name, or file path to trigger the review and generate per-role reports.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I automate pull request reviews across multiple code quality dimensions?

Automate pull request reviews by orchestrating parallel reviewer agents to assess code changes across correctness, consistency, quality, security, and architecture dimensions. Provide a PR identifier, branch name, or file path to trigger the review and generate structured per-role reports.

What's the best way to run multi-perspective code reviews on a GitHub PR diff?

Run multi-perspective code reviews on a GitHub PR diff by using a diff-driven pipeline that reads the patch file and coordinates parallel agents. This orchestrates hybrid reviewer roles to provide fast, structured feedback on your code changes.

Can I review a specific branch or file path instead of a full pull request?

Yes, you can review a specific branch or file path instead of a full pull request. The review pipeline accepts a PR identifier, branch name, or specific file path to trigger the diff analysis and generate per-role review reports.

How do parallel code review agents structure their feedback?

Parallel code review agents structure their feedback by writing per-role reports to individual markdown files. Each agent evaluates the diff from a specific dimension like security or architecture, outputting its verdict to a designated review file for aggregated results.

Do I need to prepare a diff patch file before running an automated code review?

Yes, the automated code review pipeline requires a diff patch file to exist. The diff-driven analysis reads the patch file from a designated run directory to evaluate your code changes and generate the corresponding per-role review reports.