reviewlisted

# Code Review Multi-wave review by logical code-path units (not files): per-unit deep review → cross-unit boundary review → verification of Critical findings. **Optional git range:** "$ARGUMENTS" ## Step 1: Determine Scope Precedence (first match wins): 1. Git range argument provided → `git diff <range> --name-only` 2. Working tree has changes → `git diff --name-only HEAD` (unstaged + staged) 3. PR exists (`gh pr view`) → use `base..head` as range Read the full diff for context. ## Step 2: Identify Logical Units Group by **code path**, not directory or file type. A unit is a set of files participating in one user-facing flow, background job, shared abstraction, or feature surface. Examples: - Auth flow: login + session refresh — auth router, session store, middleware - Background ingestion job — scheduler, processor, error reporter - Shared validation helper — one util used by both auth and ingestion - Schema migration — migration file + ORM models - Documentation update — README, docs Per unit: name, files, brief description, complexity (small / medium / large). ## Step 3: Confirm Units For obvious small diffs (1-2 files, single unit): state and proceed. Otherwise present and ask: ``` <N> logical units: 1. **<unit-name>** (<complexity>) — <files>: <description> 2. ... Proceed, or adjust? ``` Wrong grouping poisons downstream — ask when ambiguous. ## Step 4: Wave 1 — Per-Unit Deep Review Per unit, dispatch the reviewer fleet in parallel via Task: - `code-revi