review

# review ## Purpose Code quality analysis. Review finds bugs, bad patterns, security issues, and untested code. It does NOT fix anything — it reports findings and delegates: bugs go to rune:fix, untested code goes to rune:test, security-critical code goes to rune:sentinel. <HARD-GATE> A review that says "LGTM" or "code looks good" without specific file:line references is NOT a review. Every review MUST cite at least one specific concern, suggestion, or explicit approval per file changed. </HARD-GATE> ## Triggers - Called by `cook` Phase 5 REVIEW — after implementation complete - Called by `fix` for self-review on complex fixes - `/rune review` — manual code review - Auto-trigger: when PR is created or significant code changes committed ## Calls (outbound) - `scout` (L2): find related code for fuller context during review - `test` (L2): when untested edge cases found — write tests for them - `fix` (L2): when bugs found during review — trigger fix - `sentinel` (L2): when security-critical code detected (auth, input, crypto) - `docs-seeker` (L3): verify API usage is current and correct - `hallucination-guard` (L3): verify imports and API calls in reviewed code - `design` (L2): when UI anti-patterns suggest missing design system — recommend design skill invocation - `perf` (L2): when performance patterns detected in frontend diff - `review-intake` (L2): structured intake for complex multi-file reviews - `sast` (L3): static analysis security scan on reviewed code - L4 exten...