code-analysis

Performs structure + deep analysis of a single source file. Adapts analysis focus based on file_role (declaration, implementation, module). For implementation files, reads paired declaration mirror as context. Produces a mirror document at .codeanalyzer/mirror/{path}.md.

Run a PR-aware quality audit. Uses mcp__gitnexus__detect_changes + mcp__gitnexus__impact to identify affected subsystems, then runs Phase 2 quality-analyzer on that subset only. Fast (minutes). Use when the user wants to audit a pull request, working-tree changes, or staged changes before commit. Accepts: `/analyze-pr main..feature`, `/analyze-pr --staged`, `/analyze-pr --working-tree`, `/analyze-pr <commit>..<commit>`. Requires a prior /analyze baseline (Phase 1 must have been completed at least once).

Comprehensive source code analysis on top of GitNexus knowledge graph. Phase 1 (structure, declarations) → Phase 2 (implementation quality, per subsystem) → Phase 3 (deterministic flow + dead code via GitNexus) → Phase 4 (usage docs, optional). Supports glob and natural-language scope. Hard-requires GitNexus MCP and language-pack static tools. Use when the user wants to analyze code quality, understand project structure, or get a full codebase audit.

Phase 4: Generate API reference document. Compiles the Exports/Public API sections from Phase 1 mirror documents and class hierarchy information into a public API listing with signatures and usage examples.

Phase 4: Generate project architecture overview document. Synthesizes Phase 1 structural analysis (subsystems, dependencies, class hierarchy) and Phase 3 flow analysis (entry points, call graphs) into a comprehensive architecture description.

2 hooks across 2 events