From code-analysis
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/code-analysis:architecture-overviewopusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generates `.codeanalyzer/reports/phase4/architecture-overview.md` by pulling structured data via GitNexus Cypher and narrating with LLM.
Generates .codeanalyzer/reports/phase4/architecture-overview.md by pulling structured data via GitNexus Cypher and narrating with LLM.
.codeanalyzer/subsystems.md (already structured).MATCH (a:Module)-[:DEPENDS_ON]->(b:Module)
RETURN a.name, b.name
.codeanalyzer/state/entry-points.json (produced by Phase 3).# Architecture Overview
## 1. System Purpose
<LLM narrative, 2 paragraphs, informed by phase1 summary>
## 2. Subsystem Map
<table from subsystems.md + coupling matrix>
## 3. Module Dependency Diagram
<Mermaid flowchart from dependency Cypher>
## 4. Entry Points
<list from entry-points.json>
## 5. Cross-Cutting Concerns
<LLM narrative: subsystems with unusually high coupling, bridging modules>
npx claudepluginhub juyeongyi/jylee_claude_marketplace --plugin code-analysisGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.