review-codeReviews code for design issues and correctness bugs that static analysis misses — single responsibility, abstraction levels, testability, meaningful naming, API design, error-handling strategy, and defects you can trace to a failing input or state. Use when asked to review code, audit a module, chec
review-docsReview documentation (README.md, agent-instructions files — CLAUDE.md, AGENTS.md, or the harness's equivalent — and .claude/rules/) for accuracy, drift against the codebase, and context cost. Use whenever the user asks to review or audit docs, check documentation, validate a README, or check whether
review-testsReviews tests for issues that coverage tools miss — falsifiability, isolation hazards, dead expectations, tautological assertions, missing edge cases, and unclear test names. Use when asked to review tests, audit a test suite, check test quality, validate test isolation, or check whether tests actua