parallel-codebase-review

Dispatches parallel reviewer subagents to audit an entire codebase and synthesizes findings.

10|1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/catalystctl/catcode --skill parallel-codebase-review-catalystctl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallel-codebase-review
Source: https://github.com/catalystctl/catcode/tree/main/.catalyst-code/skills/parallel-codebase-review
Command: npx skills add https://github.com/catalystctl/catcode --skill parallel-codebase-review-catalystctl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing an entire codebase with a single agent produces shallow, uneven coverage. This Skill fans out many focused reviewer subagents in parallel, each covering a bounded slice of the code, then synthesizes their findings into one deduplicated, severity-ranked report. ## Core Features & Use Cases - Parallel fan-out review: Splits a codebase into per-module review units (roughly 1.5k LOC each) and dispatches them as parallel subagent tasks with a shared output contract of file:line evidence plus critical/high/medium/low severity. - Batch and concurrency control: Explains the soft default of 8 parallel tasks, the absolute max of 256, and how to set concurrency so large batches run together instead of queueing. - Model selection and verification: Supports per-task model overrides and a cheap single-mode probe to confirm a model resolves before dispatching a large batch. - Synthesis and verification: Dedupes findings across reviewers, groups them by severity, writes a full REVIEW.md report, and re-reads cited lines to verify surprising Critical claims. - Use Case: When asked to audit a whole repository, launch 12 reviewers (6 for the Rust core, 3 for the Go TUI, plus SDK, web, and build/CI) in one parallel call, then deliver an executive summary with a prioritized fix list. ## Quick Start Review this entire codebase by fanning out parallel reviewer subagents per module and synthesize the findings into a severity-ranked report.

Frequently Asked Questions about parallel-codebase-review

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

FAQPage Schema
How do I review an entire codebase with AI subagents?

Map the directory structure and file sizes first, then split the code into review units of roughly 1.5k lines each. Dispatch one reviewer subagent per unit in a single parallel call, giving each the exact files, focus areas, and an output contract of file:line evidence with severity ratings.

How many parallel subagent tasks can run at once?

The parallel tasks mode has a soft default max of 8, but larger batches are allowed up to an absolute max of 256. Extra tasks queue under the concurrency semaphore, so set concurrency to the batch size when you want them all running together.

When should I not use parallel codebase review?

Skip it for targeted reviews of a single file or feature, which you can just read and review directly. It is also unnecessary when there are fewer than about three review units, since one reviewer subagent suffices.

Can each reviewer subagent use a different model?

Yes, per-task model overrides are supported by passing a model field on each task. Verify the model resolves first with one cheap single-mode test, since an unresolvable model fails instantly without running.

Why do reviewer subagents report wrong line numbers?

Reviewer models can drift on line numbers, especially on large files. For any surprising or high-stakes Critical finding, re-read the cited lines yourself before reporting it, converting the claim from reviewer assertion into a verified fact.