Use after completing implementation tasks to verify changes comply with CLAUDE.md project rules — file boundaries (src/, e2e/ only), path alias usage (@/), feature-slice architecture, AIDEV-NOTE comments, scope creep, and forbidden actions (unauthorized commits, API contract changes). NOT for general code quality …
Use after writing or modifying code to review for over-engineering, unnecessary complexity, anti-patterns, and feature-slice architecture compliance. Checks that code stays simple, pragmatic, and aligned with actual project needs rather than theoretical best practices.
Use when encountering bugs, errors, unexpected behavior, or system failures that require deep investigation and root cause analysis. Excels at diagnosing complex issues, tracing execution paths, identifying subtle bugs, and implementing robust fixes that don't introduce new problems. Perfect for production issues…
Audits GitHub Actions workflow YAML and composite-action YAML for supply-chain, injection, permission, and secret-handling defects. Advisory-only (no self-heal). One member of the Code Audit Team gate.
Maintainer-only audit of framework bash and the bats suites guarding it: quoting/portability correctness, a shellcheck oracle, and conditional hook-contract and bats-suite lenses. Advisory-only (no self-heal). One member of the Code Audit Team gate.
Advisory test-worthiness audit for the emergent surface. Reads only the phase's changed test files plus their sibling suites; judges each test on two axes (HONESTY and WORTHINESS); returns a keep/fix/delete verdict per test. Proposes only, edits no files, every delete is human-gated.