deep

Deep Code Review (PLN-807 + FEA-1401)

This command is shorthand for /start --depth deep. Follow every instruction in ${CLAUDE_PLUGIN_ROOT}/commands/start.md verbatim, with one binding:

DEPTH = "deep" for the entire run. Pass --depth deep to every helper that accepts the flag (notably prepare-run, hygiene, review-state-read, and review-state-write).

What deep does

Deep produces the standard fleet plus two deep-only conditional core reviewers: the always-on Design Critic and the signal-gated Impact Analyzer (FEA-1401).

The Design Critic runs on every deep review (no trigger required). It evaluates the change for software-design craftsmanship — module depth and information hiding, SOLID adherence, dependency direction and layer boundaries, and project/package structure — drawing on A Philosophy of Software Design, the SOLID principles, and Clean Architecture. It flags only design flaws this change introduces or demonstrably worsens (a new shallow module, a wrong-direction dependency, a god-class this PR grew, a type-switch it extended), runs on Sonnet, and is exempt from the domain-critic cap (it is a source: "core" reviewer, not a project-specific critic). Like the Impact Analyzer it is code-intelligence-aware: when the operator's session provides an MCP server that indexes the repo, it uses that server for module/layer layout and for dependency direction and import cycles, falling back to grep otherwise. The plugin is substrate-agnostic — it names no particular server and works with whichever one is connected. Findings carry category: "Code Quality".

The Impact Analyzer (FEA-1401) spawns when signal extraction detects exported_symbol_change or symbol_deletion in the diff. It identifies changed exported symbols (function signatures, type definitions, exported constants, class API, schema fields, deletions), greps the codebase for external usages outside the diff, and emits findings whose external_impact[] array lists every callsite that breaks under the new signature.