multi-agent-codebase-auditlisted

# Multi-agent codebase audit Review a **whole repository** with a fleet of agents. The hard constraint that shapes everything: **a codebase doesn't fit in one agent's context** — so you can't just "review the repo." You **partition → fan out → reduce**: split the repo into slices that each fit a context, audit each slice in its own subagent in parallel, then reconcile across slices to catch what no single slice can see. This is the **whole-repo** sibling of [`dual-agent-review`](../dual-agent-review/SKILL.md) (which reviews **a diff**). It **reuses that skill's triage → fix → report machinery** — see it for those steps; this skill adds the map/partition/reduce layer on top. Partitioning heuristics, the auditor/critic prompts, and the coverage-ledger template live in [`reference/partition-and-prompts.md`](./reference/partition-and-prompts.md). ## When to use (and not) - **Use for:** a periodic deep audit, a pre-release security/quality sweep, onboarding an inherited/unfamiliar repo, or a post-incident "what else is like this?" sweep. - **Don't use for:** per-change review — that's a diff, use `dual-agent-review`. A whole-repo audit is **expensive**; scope it (a subtree, a risk area) when you don't need everything. ## The flow ```text 1. MAP repo ─► 2. PARTITION (slices that fit a context) ─► 3. FAN OUT auditors (parallel/bg) │ one+ per slice