aio-review-deep

Fleet Review — Parallel Multi-Agent Code Review

Dispatches a fleet of specialized review agents in parallel, each scrutinizing the diff through a different lens (security, architecture, quality, performance, tests). Uses GitNexus + CodeWiki for deep codebase understanding, then runs adversarial meta-review to synthesize findings. Heavier than aio-review-quick (quick pre-commit sanity check) — reach for this before merging high-impact changes.

Environment

• GitNexus: !npx gitnexus status 2>/dev/null && echo "AVAILABLE" || echo "NOT INSTALLED"
• CodeWiki: !which codewiki 2>/dev/null || echo "NOT INSTALLED"

When to Use

• User requests "review code", "code review", "review this PR"
• Before merging a pull request
• After implementing a major feature
• User wants quality assessment grounded in codebase structure

Workflow

Phase 0: Detect Tools and Language/Domain

0.1 Tool Availability

Tools are pre-detected in the Environment section above. Adapt the review based on availability:

Tool	Status	Impact on Review
GitNexus	Available	Hybrid search, symbol context, dependency tracking, blast radius via impact
GitNexus	Missing	Fall back to CodeWiki dependency graphs + manual grep for impact
CodeWiki	Available	Module clustering, metrics, dependency graphs
CodeWiki	Missing	Skip module mapping — use GitNexus context or file-path grouping

Proceed with whatever tools are available. Both together give the richest review; either subset still works.

0.2 Detect Language/Domain and Invoke Specialist Skills

Scan the project and changed files to invoke domain-specific static analysis before the general review agents run. Each skill brings specialized linters and pattern checks that general agents cannot replicate.

# Language detection — invoke matching skills
if go.mod or *.go exists:
  → invoke /golang-mastery (go vet, golangci-lint, govulncheck, nilaway, deadcode, race detection)

if *.xcodeproj or Package.swift exists:
  → invoke /ios-mastery (SwiftUI patterns, iOS conventions, Liquid Glass compliance)

# Framework detection — scan changed files for imports
if changed files import "react" or "next":
  → invoke /react-minimal-effects (useEffect anti-patterns, React 19 hooks, React Compiler readiness)

if changed files import "xstate":
  → invoke /xstate (v5 strict patterns, setup().createMachine(), actor patterns)

# Domain detection — based on file paths
if changed files touch infra/, deploy/, monitoring/, or include logging/metrics/tracing code:
  → invoke /monitoring-observability (Golden Signals, OpenTelemetry, SLO compliance)