What problem does it solve?
Architecture health often deteriorates due to layer violations, hidden god objects, and inconsistent boundary rules. This skill provides a repeatable, quantifiable approach to map a codebase into layers, detect violations, score critical constructs, and guide safer refactors.
Core Features & Use Cases
- Layer mapping: classify codebase components into Presentation, Application, Domain, and Infrastructure layers.
- Violation detection: identify upward dependencies that breach layer rules and flag model/service/controller issues.
- Callback scoring: apply a 1-5 score per callback to surface architectural concerns.
- God object detection: highlight high-churn files with complexity metrics to pinpoint responsibilities clusters.
- Quality gates: enforce target metrics to guide quality improvements before refactors.
- Use cases: onboarding a new team, planning major refactors, or quarterly health checks.
Quick Start
Analyze a repository by running the architecture analysis workflow to generate a health-check report you can review and action.