review-architecture

To audit codebase architecture, the skill traces actual file imports, entry points, and tests to evaluate structural boundaries and dependency directions, producing a scored diagnostic report with a Mermaid dependency graph and concrete improvement guidance.

Architectural fitness scoring evaluates codebase health across dimensions like boundary quality, dependencies, abstraction, DRY, extensibility, testability, and parallelisation, generating a multi-dimensional scorecard with actionable findings grounded in real file analysis.

Generating a dependency graph from codebase imports involves tracing actual file relationships and entry points, which this skill does automatically, outputting a Mermaid diagram of import relationships with notes highlighting architectural violations.

Yes, you can use this architecture review tool on any codebase by pointing it at the repository root. It requires no external dependencies or components, reading actual files directly to ground its diagnostic findings in reality.

You should re-run a codebase architecture health assessment after major structural changes, as the skill provides recommended review cycles and handoff guidance indicating optimal cadences for re-evaluating dependency directions and abstraction fitness.

The best way to diagnose architectural integrity is reading actual repository files to trace imports, entry points, and tests, evaluating boundaries and abstraction fitness to produce a comprehensive codebase summary with scored findings and improvement guidance.