dyad:multi-pr-review

Coordinate multi-agent PR reviews to surface consensus-backed issues from code diffs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/HeXx123321/proteaos-demo --skill dyad-multi-pr-review-hexx123321
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dyad:multi-pr-review
Source: https://github.com/HeXx123321/proteaos-demo/tree/main/.claude/skills/multi-pr-review
Command: npx skills add https://github.com/HeXx123321/proteaos-demo --skill dyad-multi-pr-review-hexx123321

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Multi-agent PR reviews help engineering teams surface high-quality issues in code changes by coordinating multiple Claude-based reviewers to reduce bias and provide a consolidated assessment.

Core Features & Use Cases

  • Spawns three independent sub-agents to review PR changes, each receiving files in a different randomized order.
  • One agent focuses specifically on code health and maintainability; Agents 2-3 handle correctness, bugs, and security.
  • Aggregates findings using consensus voting so only issues identified by two or more agents are reported, with at least one MEDIUM or higher severity.
  • Deduplicates against existing PR comments to avoid duplicate feedback and noise.
  • Always posts a summary, with low priority issues rendered in a collapsible section for context.

Quick Start

Run the orchestrator with a PR diff to generate consensus issues and post a summary.

Frequently Asked Questions about dyad:multi-pr-review

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

FAQPage Schema
How do I run a multi-agent pull request review to reduce bias on code diffs?

Multi-agent pull request review reduces bias by spawning three independent sub-agents to review changes. Each agent receives files in a randomized order, with one focusing on code health and others on correctness and security.

How does consensus voting work for aggregating code review findings?

Consensus voting aggregates code review findings by only reporting issues identified by two or more agents. Reported issues must also meet a minimum threshold of MEDIUM or higher severity to ensure high-quality feedback.

Can I prevent duplicate feedback when running automated code reviews on existing PR comments?

Yes, automated code reviews deduplicate findings against existing PR comments. This prevents duplicate feedback and reduces noise by ensuring only new, consensus-backed issues are surfaced in the summary.

What is the best way to review large pull requests with diverse file changes?

The best way to review large pull requests is distributing files among multiple agents with randomized orders. This approach covers diverse file changes while maintaining focused analysis on correctness, security, and code health.

Do I need an anthropic dependency to perform consensus-driven PR analysis?

Yes, you need an anthropic dependency to perform consensus-driven PR analysis. The multi-agent coordination relies on Claude-based reviewers to independently analyze diffs and submit JSON-based issue schemas for aggregation.

Can I configure the agent count and consensus threshold for diff analysis?

Yes, diff analysis supports a configurable agent count, consensus threshold, and extended thinking budgets. This allows you to adjust the depth of the code review and the strictness of issue reporting.