mac

Read-only deep analysis role. Diagnose problems, analyze codebases, and recommend approaches with file:line evidence. Never writes or edits files. Use for build request analysis, complex PR reviews, debugging investigations, and architecture questions.

Pre-flight check before implementation work. Verifies a repo has the foundational dev guardrails (test framework, linting, type checking) the build cycle depends on, and reports a READY / BLOCKED verdict the workflow uses to gate.

Inspect and analyze codebases using pygount for LOC counting, language breakdown, and code-vs-comment ratios. Use when asked to check lines of code, repo size, language composition, or codebase stats.

Review a code change (a PR diff or a working-tree diff) for correctness, security, quality, testing, performance, and docs. Produces a structured verdict; does not post it.

Use when encountering any bug, test failure, or unexpected behavior. 4-phase root cause investigation — NO fixes without understanding the problem first.

Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with test-first approach.