multi-agent-pr-review

Dispatches parallel subagents to build a pre-read review guide for GitHub pull requests.

Updated Apr 3, 2021
One-click install
npx skills add https://github.com/shrik450/dotfiles --skill multi-agent-pr-review-shrik450
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-agent-pr-review
Source: https://github.com/shrik450/dotfiles/tree/main/dot_claude/skills/multi-agent-pr-review
Command: npx skills add https://github.com/shrik450/dotfiles --skill multi-agent-pr-review-shrik450

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a large or complex pull request requires hours of up-front investigation before you can even start forming opinions. This Skill does that investigation for you by dispatching parallel subagents across distinct review concerns, then synthesizing their findings into a concise review guide — so you walk into the PR already oriented, without anyone pre-writing your verdicts. ## Core Features & Use Cases - Primer agent: A single agent first writes a factual primer covering the PR's purpose, file-by-file map, key concepts, test inventory, and existing review comments. - Four parallel investigation agents: Style & CLAUDE.md adherence, correctness (with git history analysis), tests & coverage gaps, and design & code quality informed by a mined reference of your real past review comments. - Guide, not verdicts: The output is a structured review guide — hotspots, open questions, cross-cutting observations, and a "verified fine" section — never a ready-to-post review, and nothing is ever posted to GitHub. - Use Case: You are assigned a 15-file PR touching LLM prompt logic. Invoke the Skill, get a 2-minute orientation, 3-7 hotspots with path:line citations, and a dossier for drill-down, then write your own 5-10 inline comments in a fraction of the usual time. ## Quick Start Ask the assistant to run the multi-agent PR review on PR number 123 and produce a review guide for you to read before reviewing it yourself.

Frequently Asked Questions about multi-agent-pr-review

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

FAQPage Schema
How do I review a large pull request faster with AI agents?

Dispatch parallel subagents that each investigate one concern — style, correctness, tests, and design — then synthesize their findings into a review guide. This Skill orchestrates exactly that workflow and outputs hotspots with path:line citations instead of pre-written verdicts.

Does this Skill post review comments to GitHub automatically?

No. The Skill is explicitly read-only: it never posts comments via gh, never edits the branch, and never pre-writes your review. The output is an inline guide that helps you form your own review.

What tools are required to run a multi-agent PR review?

The workflow relies on the GitHub CLI (gh) for PR metadata, diffs, and existing review comments, plus git commands like log, blame, and diff for regression analysis. Subagents are spawned through the Agent tool.

When should I not use the four-agent PR review split?

Skip the four-way split for small PRs under roughly 200 lines or fewer than 5 files — a single agent doing all passes is enough. Pure-documentation PRs should just be read directly, and PRs without tests can drop the testing agent.

How does the design review agent learn my review style?

It reads a cached reference file distilled from roughly 70 of your real past review comments, learning which design concerns you prioritize. The guide is refreshed only periodically, never refetched live during a review run.