/performing-multi-agent-code-review

name: performing-multi-agent-code-review
description: Perform a rigorous, multi-agent code review with architecture-compliance, parallel quality/security analysis, finding validation, and severity audit. Use when the user asks for a structured, deep, thorough, multi-pass, or multi-agent code review — or a review that includes architecture/pattern compliance, confidence-scored findings, or a severity audit. Use when the user asks for a code review across a commit range, time window, or N most recent commits in a locally checked-out repo.
allowed-tools: "Bash(gh pr diff:*), Bash(gh pr view:*), Bash(git diff:*), Bash(git status:*), Bash(git rev-parse:*), Bash(git log:*), Read, Write, Grep, Glob, Skill, AskUserQuestion"
argument-hint: "[pr-number | commit-range] [--model <model>] [--model-analysis <model>] [--model-security <model>] [--model-validation <model>] [--model-audit <model>] [--output-dir <path>]"

Overview

Execute a structured, multi-agent code review on a set of code changes. Follow the process below precisely — skipping steps degrades consistency and accuracy.

Prerequisites

This skill depends on the following sibling plugins.

• **`bitwarden-security-engineer`**

`claude-config-validator` and `plugin-dev` are **optional** enhancers, not prerequisites — when present they power the conditional Claude-configuration agent (Agent 4) and skill-review agent (Agent 5) in Step 3; when absent, those agents do not run and the rest of the pipeline runs unchanged apart from the Step 7 coverage line. Detect them by the same resolvability signal described below, but never abort on one. Do not add either to the abort check.

Agent 5's omission is recorded in the report (see Step 7); Agent 4's is not.

Before Step 1, verify each prerequisite plugin is installed. The signal is resolvability — a required subagent type or skill that does not appear in your available tooling means the plugin is missing. If any is missing, **abort with the message below** — do not proceed with a degraded pipeline.

> Prerequisite plugin `<name>` is not installed. Install it and retry. Review aborted.

Output Location

If `--output-dir <path>` is present in `$ARGUMENTS`, resolve immediately upon invocation and use that path verbatim. Otherwise, default to `${CLAUDE_PLUGIN_DATA}/code-reviews/`. Do not test whether it exists, prompt the user to confirm, nor offer alternatives. If the caller passed a bad path, the write in Step 9 will fail and surface the error.

Model Selection

Resolve per-stage models upon invocation before Step 1 begins.

Flag values are the Agent tool's model nicknames, in ascending tier order: `haiku` < `sonnet` < `opus`. The **global model** is `--model` if specified, otherwise the session's model.

| Stage | Agents | Flag | Default | | -------------- | --------------------------------------------------------------- | -------------------- | ---------- | | Analysis | Step 2 architect; Step 3 Agents 1–2, and conditional Agents 4–5 | `--model-analysis` | global | | Security | Step 3 Agent 3 (security & logic) | `--model-security` | global | | Validation | Step 4 | `--model-validation` | global | | Severity audit | Step 5 | `--model-audit` | **sonnet** |

Each stage resolves to its flag if present, otherwise its default; an explicit `--model` also overrides the audit's sonnet default.

**Security floor.** `--model-security` may only pin at or above the global model. On a lower pin, run security at the global model and note the ignored pin in the announcement. Rationale: P01–P06 evaluation quality must not silently degrade.

**Analysis downgrade caveat.** Bugs missed by a cheaper analysis model cannot be recovered by downstream validation.

**Announce** the resolved stage → model table before starting the review.

**Steps 6–9 run in the main agent** — the merge needs the full finding state and reference content in context. One model per stage; parallel same-stage runs collide finding IDs.

Operating Rules

Applies to all agents and subagents.

• Don't write to GitHub. All findings go to a local markdown file.
• Tool discipline (see Orchestration → Tool Discipline) applies to the main agent and is propagated verbatim to every subagent except Agent 5, which takes the variant in `references/agent-5-skill-review.md`. Rationale for the WebFetch/WebSearch ban: bypasses `gh` auth, skips audit trails, can return stale cached pages.

Orchestration

Project Preamble Propagation

Subagents do not inherit the main agent's CLAUDE.md context. Every subagent prompt in Steps 2–5 MUST open with the two required blocks below, in order, followed by the conditional block if it applies.

Agent 5 is a full exception to this section: it never classifies severity or reasons about vault data, because it returns prose and the orchestrator classifies in Step 3, so the security-context directive has nothing to act on. The two sections that follow apply to it in modified form. Read the carve-out under Review Rules, and the reference it points to, before assembling its prompt.

**Required — Bitwarden security context.** Include this directive verbatim:

> At the start of your analysis, invoke `Skill(bitwarden-security-engineer:bitwarden-security-context)`. Use its principles, vocabulary, and requirement categories verbatim when classifying findings — do not paraphrase.

**Required — zero-knowledge and threat-model preamble.** Include this block verbatim in the subagent prompt:

> **Zero-knowledge invariant.** Bitwarden servers only store and synchronize encrypted vault data. The server, Bitwarden employees, and third parties must never be able to access unencrypted vault data. Encryption and decryption happen client-side only. The Master K