← ClaudeAtlas

multi-code-reviewlisted

MUST USE when a branch needs N independent whole-branch code review rounds with fixes applied between rounds. M clean-context reviewer subagents per round (default 1) under a rotating lens (correctness/spec alignment, adversarial red-team, security, test quality); one fix subagent per round for Critical/Important findings; sidecar audit log; early exit after two consecutive clean rounds. Invoked by subagent-driven-development at the final whole-branch review gate, or directly via /multi-code-review [BASE] [N|N=<n>] [M=<m>]. Triggers on: "multi code review", "independent code reviews", "several code reviews", "review the branch N times", "code review rounds", "whole-branch review loop".
brunob54/superpowers-orchestrator · ★ 3 · Code & Development · score 76
Install: claude install-skill brunob54/superpowers-orchestrator
# Multi-Code-Review Run an N-round independent review-fix-repackage loop on a branch diff using subagents. Each round is blind to the authoring conversation and to prior rounds' findings — that independence is the point. ## Required Start Announce: `I'm using multi-code-review to review this branch.` **Platform check:** this skill requires the Agent tool. On platforms without it (Codex, Cursor), refuse with one line — "multi-code-review requires subagent dispatch (Agent tool), which this platform lacks" — and stop. (The subagent-driven-development gate falls back to its single-pass final review on such platforms; that fallback lives there, not here.) ## Parameters - **Review range `BASE..HEAD`:** the SDD gate passes MERGE_BASE (the commit the branch started from). Direct invocation: if the user gave a BASE, reject it outright unless it matches a conservative ref charset — `^[A-Za-z0-9._/~^{}-]+$`, i.e. no `$`, backtick, `;`, `|`, `&`, parenthesis, or newline — because quoting alone does not stop command substitution, and the argument reaches the shell as literal text. Assign it to a shell variable and reference that variable; never paste the user's text straight into a command string. Then resolve and verify with `git rev-parse --verify --quiet "$BASE^{commit}"`; stop and report on failure. Use the resulting SHA — never the raw argument — for every later command, including the ancestry check below, reducing it to `git merge-base <resolved-SHA> HE