code-review-orchestrator

Orchestrates parallel code reviews across design, correctness, and quality lenses into a unified verdict.

1|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/D1ssolve/craft-agents --skill code-review-orchestrator-d1ssolve
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-orchestrator
Source: https://github.com/D1ssolve/craft-agents/tree/main/skills/code-review-orchestrator
Command: npx skills add https://github.com/D1ssolve/craft-agents --skill code-review-orchestrator-d1ssolve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing large code changes with a single pass often misses issues because one reviewer cannot simultaneously focus on architecture, correctness, and performance. This Skill splits the review into focused parallel sub-reviews and merges the findings into one deduplicated, ranked report. ## Core Features & Use Cases - Scope-Based Mode Selection: Automatically chooses a minimal single-agent review for trivial changes or a full three-agent review for substantive ones. - Parallel Lens Reviews: Launches three concurrent code-reviewer agents covering Design & Architecture, Correctness & Verification, and Quality & Performance. - Aggregated Verdict Report: Deduplicates overlapping findings, ranks them Critical/Important/Minor, preserves file:line references, and produces a merge-readiness verdict. - Use Case: After implementing a feature branch, run this Skill to get a structured multi-perspective review with concrete fixes, then dispatch a backend-developer agent to resolve Critical and Important issues. ## Quick Start Review the changes between BASE_SHA and HEAD_SHA on this branch using parallel focused code reviews and give me an aggregated verdict.

Frequently Asked Questions about code-review-orchestrator

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

FAQPage Schema
How do I run a parallel code review with multiple reviewers?▼

Provide the change description, requirements, and commit range, and the orchestrator launches three code-reviewer agents in a single response, each with a distinct lens. Their findings are then deduplicated, ranked by severity, and merged into one report.

What review perspectives does a multi-agent code review cover?▼

It covers three lenses: Design & Architecture (SOLID, coupling, module boundaries), Correctness & Verification (logic, edge cases, error handling, tests), and Quality & Performance (N+1 queries, complexity, memory, concurrency, naming).

When does the orchestrator skip the full multi-agent review?▼

Trivial changes such as config edits, comment updates, or diffs under 20 lines with no logic changes trigger Minimal mode with a single agent and no lens. All other changes use the standard three-agent review.

How are duplicate findings from different reviewers handled?▼

Issues appearing across multiple lenses are deduplicated and kept once with combined tags. Findings are then ranked Critical, Important, or Minor while preserving file:line references and concrete fix suggestions.

What happens after the aggregated code review report is generated?▼

The receiving-code-review skill is loaded to evaluate the findings, and a backend-developer agent is launched to address Critical and Important issues identified in the report.