Deep architectural analysis of a codebase - structure, patterns, coupling, and evolution
npx claudepluginhub crazymeal/claude-architect-marketplace --plugin architecture-analysisdirectoryopus# Codebase Analysis Comprehensive architectural analysis of an existing codebase. ## Scope **DO**: Analyze structure, identify patterns/anti-patterns, assess coupling, evaluate evolution readiness, produce report with diagrams **DON'T**: Modify code, implement fixes ## Analysis Framework ### 1. Structural Analysis - Entry points and boundaries - Module/package organization - Layering discipline - Dependency direction (outside-in or violations) ### 2. Pattern Recognition Identify architectural style: layered, hexagonal, clean, vertical slice, microservices, event-driven, or hybrid. L...
/analyze-codebaseGenerates a detailed report analyzing codebase structure, file tree, counts, sizes, configuration files, and key source locations like entry points, routes, models, and components.
/analyze-codebaseGenerates a detailed report analyzing codebase structure, file tree, counts, sizes, configuration files, and key source locations like entry points, routes, models, and components.
/analyze-codebaseGenerates a detailed report on codebase structure: directory tree, file counts/sizes, configs (package/build/CI/Docker), and key files (entries/routes/models/components/DB).
/analyze-codebaseAnalyzes codebase as enterprise digital transformation advisor, producing strategic assessments of technology capabilities, business impact, innovation opportunities, risks, and growth strategies.
/analyze-codebaseGenerate comprehensive analysis and documentation of entire codebase
/analyze-codebaseGenerate comprehensive analysis and documentation of entire codebase
Comprehensive architectural analysis of an existing codebase.
DO: Analyze structure, identify patterns/anti-patterns, assess coupling, evaluate evolution readiness, produce report with diagrams
DON'T: Modify code, implement fixes
Identify architectural style: layered, hexagonal, clean, vertical slice, microservices, event-driven, or hybrid.
Look for DDD tactical patterns: aggregates, repositories, domain events, value objects.
Categorize as: Reckless-Deliberate, Reckless-Inadvertent, Prudent-Deliberate, Prudent-Inadvertent
Write all outputs to files:
| Artifact | Location |
|---|---|
| Analysis report | docs/analysis/analysis-[name]-[date].md |
| Current state diagram | docs/diagrams/c4-container-current-[name].puml |
| Dependency graph (if issues) | docs/diagrams/dependencies-[name].puml |
# Architecture Analysis: [Name]
## Executive Summary
[2-3 sentences: overall assessment]
## Key Findings
### [Finding 1]
**Evidence**: [file:line references]
**Impact**: [High/Medium/Low]
**Recommendation**: [Action]
## Patterns Identified
## Anti-Patterns Detected
## Technical Debt Assessment
## Evolution Recommendations
If ending without artifacts: "Let me produce the analysis report and diagrams."