aio-review-deeplisted

# 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. B