improve-codebase-architecture

An architectural codebase review identifies shallow modules by surfacing friction like leaking seams and hard-to-test logic. It then generates an HTML report with before/after diagrams and ranked refactor candidates to guide your deepening efforts.

A deepening opportunity in software architecture is the chance to turn a shallow module into a deep one. This improves testability, locality, and AI-navigability by resolving logic that is hard to test through its current interface.

Generate a self-contained HTML architectural review report by scanning the repository. The output includes before-and-after diagrams, problem-solution-benefit cards, ADR conflict handling, and a ranked top recommendation to tackle first.

Yes, you can perform repository-level architectural reviews to check for friction across the whole codebase. The review applies domain-aware exploration to detect shallow modules, leakage paths, and seams that leak across the project.

No dependencies are required to run the architectural codebase analysis. The skill operates independently to review project domain vocabulary and produce a self-contained HTML report with visual deepening opportunities.

The best way to prioritize codebase refactoring candidates is to generate an architectural review that ranks recommendations by strength. It provides a top recommendation to tackle first, supported by before/after diagrams and problem-solution-benefit cards.