review

Code Review

$ARGUMENTS

Reviews code changes for quality and issues.

Changed files context

• Changes: !git diff --stat main...HEAD 2>/dev/null || git diff --cached --stat 2>/dev/null || echo "no changes detected"

Signal Collection (never stop at the first red)

Collect every failing signal up front, then review the diff in full anyway:

Signal	How to read it
Merge conflict with base	gh pr view --json mergeable,mergeStateStatus or git merge-tree
Failing CI checks	gh pr checks or the platform equivalent
Lint / typecheck failure	the project's own commands

Each failing signal becomes a blocker finding. None of them ends the run.

A review that aborts on the first red signal spends the whole cycle repeating what the tracker already displayed, while the finding that would have told the author something new never gets written. One invocation produces the most complete picture of the change that it can.

Automated Diff Analysis

Before starting manual review, run the diff analyzer script to get a structured risk assessment:

python3 ${CLAUDE_SKILL_DIR}/scripts/diff-analyzer.py [base_branch]
# Default base branch: main
# Example: python3 ${CLAUDE_SKILL_DIR}/scripts/diff-analyzer.py develop

The script outputs JSON with:

• files: each changed file with additions, deletions, category (security/test/config/migration/infra/docs/logic), and risk level
• risk_score: overall assessment (high/medium/low)
• hotspots: top 5 files by additions
• secrets_scan: potential secret leaks detected in added lines
• test_coverage_estimate: whether test files accompany logic changes (good/partial/none)
• parallel_review_recommended: boolean flag

If the script reports parallel_review_recommended: true, use the Parallel Review (Agent Teams) mode below.

---

Parallel Review (Agent Teams)

For significant PRs or large changesets, create a parallel review team:

Create an agent team to review [target]:
- Teammate 1 (security-auditor): "Review for security vulnerabilities, auth issues,
  injection risks, secret leaks. Report with severity ratings." Use Opus.
- Teammate 2 (performance-optimizer): "Check for N+1 queries, memory leaks,
  unnecessary allocations, caching opportunities. Report with impact ratings." Use Opus.
- Teammate 3 (test-engineer): "Validate test coverage, edge cases, mock quality,
  missing assertions. Report coverage gaps." Use Opus.
Each reviewer should report findings independently. Do NOT modify files.