solo-review

# /review This skill is self-contained — follow the instructions below instead of delegating to external review skills (superpowers, etc.) or spawning Task subagents. Run all checks directly. Final quality gate before shipping. Runs tests, checks security, verifies acceptance criteria from spec.md, audits code quality, and generates a ship-ready report with go/no-go verdict. ## Live Context - Branch: !`git branch --show-current 2>/dev/null` - Diff stats: !`git diff --stat HEAD~3..HEAD 2>/dev/null | tail -5` ## When to use After `/deploy` (or `/build` if deploying manually). This is the quality gate. Pipeline: `/deploy` → **`/review`** Can also be used standalone: `/review` on any project to audit code quality. ## MCP Tools (use if available) - `session_search(query)` — find past review patterns and common issues - `project_code_search(query, project)` — find similar code patterns across projects - `codegraph_query(query)` — check dependencies, imports, unused code If MCP tools are not available, fall back to Glob + Grep + Read. ## Pre-flight Checks ### 1. Architecture overview (if MCP available) ``` codegraph_explain(project="{project name}") ``` Returns: stack, languages, directory layers, key patterns, top dependencies, hub files. Use this to detect stack and understand project structure. ### 2. Essential docs (parallel reads) - `CLAUDE.md` — architecture, Do/Don't rules - `docs/plan/*/spec.md` — acceptance criteria to verify (REQUIRED) - `docs/plan/*/plan.md` ...