review

Code Review

Pre-merge review of completed work against the original plan, by one senior reviewer agent. It runs in this session.

When the user opts in, five lens reviewers find defects instead, then verifier agents try to refute each finding, and only what survives is reported as confirmed.

Announce: "Using review to assess this work before merge."

The Iron Law

NO MERGE WITHOUT CODE REVIEW

Context

The plan or requirements being reviewed: $ARGUMENTS

Step 1: Scope the diff

BASE_SHA=$(git merge-base HEAD main 2>/dev/null || git merge-base HEAD develop 2>/dev/null || git merge-base HEAD master 2>/dev/null)
git diff --stat $BASE_SHA..HEAD
git diff --name-only $BASE_SHA..HEAD

• Empty diff: print Nothing to review: HEAD has no commits beyond <base>. (naming the base branch) and stop.
• Uncommitted tracked changes (git status --porcelain): say in one line that they are not part of this review.
• The plan is $ARGUMENTS when it names a file. Otherwise the plan is the description, or none.

Step 2: Pick the reviewer

The swarm is a workflow, and the Workflow tool launches only on the user's opt-in. Opt-in means the user typed /turbocharge:review, or asked in their own words for the swarm, a multi-agent or multi-lens review, or a workflow. This skill reaching you some other way is not an opt-in: you invoked it yourself from a plain request ("check my branch before I merge"), or another skill chained into it.

• Opt-in → Step 3.
• No opt-in → Single reviewer.

Never review inline when an agent can do it. The inline review is only for No agent here.

Step 3: Launch the swarm

Call the Workflow tool with name: "turbocharge:review-swarm" and these args as JSON:

{"base": "<BASE_SHA>", "head": "<HEAD sha>", "files": ["<name-only list>"], "plan": "<plan file path or description>", "context": ["<paths>"], "stat": "<git diff --stat output>"}