dyad:multi-pr-review

Review pull request diffs with three Claude sub-agents and consensus voting.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/SL-IT-AMAZING/SLIT-ANYON --skill dyad-multi-pr-review-sl-it-amazing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dyad:multi-pr-review
Source: https://github.com/SL-IT-AMAZING/SLIT-ANYON/tree/main/.claude/skills/multi-pr-review
Command: npx skills add https://github.com/SL-IT-AMAZING/SLIT-ANYON --skill dyad-multi-pr-review-sl-it-amazing

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Multi-agent PR review system that spawns three independent Claude sub-agents to review diffs. Each agent receives files in different randomized order to reduce ordering bias. One agent focuses specifically on code health and maintainability. Results are aggregated using consensus voting - only issues identified by 2+ agents where at least one rated it medium or higher severity are reported. Automatically deduplicates against existing PR comments. Always posts a summary (even if no new issues), with low priority issues mentioned in a collapsible section.

Core Features & Use Cases

  • Spawns three independent sub-agents, each receiving files in a different randomized order to reduce bias.
  • Agent 1 focuses on code health (maintainability, clarity, abstractions); Agents 2-3 cover default focus (correctness, bugs, security).
  • Issues are classified as HIGH/MEDIUM/LOW; consensus requires 2+ agents and at least one MEDIUM or higher severity.
  • Deduplicates against existing PR comments to avoid duplicates.
  • Posts a summary report and inline comments for HIGH/MEDIUM issues, with a collapsible section for low priority items.

Quick Start

Run the orchestrator script against a PR diff to trigger the full multi-agent review workflow.

Frequently Asked Questions about dyad:multi-pr-review

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

FAQPage Schema
Does automated PR diff review focus on code maintainability or just security?

Multi-agent code review works by spawning independent sub-agents to analyze PR diffs simultaneously. Each agent reviews changed files in a different randomized order to reduce bias, with specific agents focusing on code health, correctness, bugs, and security before aggregating findings through consensus voting.

How do I automate PR review with consensus voting using Claude?

Automate PR review by running an orchestrator script against a PR diff to trigger the multi-agent review workflow. The system spawns three Claude sub-agents, aggregates their findings, and automatically posts a summary report with inline comments for issues that meet the consensus threshold.

Can I adjust the severity threshold and number of agents for automated PR reviews?

Yes, you can adjust the number of agents, consensus threshold, minimum severity, thinking budget, and max tokens. Only issues identified by two or more agents where at least one rated it medium or higher severity are reported in the final summary.

How does the consensus voting system deduplicate existing PR comments?

The consensus voting system deduplicates by checking aggregated findings against existing PR comments before posting. This prevents redundant feedback, ensuring only newly identified issues that meet the consensus threshold are posted as inline comments.

What is the best way to reduce ordering bias in automated code review?

The best way to reduce ordering bias is to provide each independent review agent with the changed files in a different randomized order. This ensures no single agent is influenced by the sequence in which files are presented during the diff analysis.

What happens when a multi-agent PR review finds no new high severity issues?

When no new high or medium severity issues are found, the multi-agent PR review still posts a summary report. Any low priority issues identified are included in a collapsible section at the bottom of the summary.