improve-codebase-architecture

To find shallow modules for refactoring, analyze your repository architecture to identify tightly coupled logic and weak seams. This Skill scans your codebase to locate shallow modules and proposes deepening opportunities that improve leverage, locality, and testability across call sites.

A deep module in software architecture provides a simple interface that hides complex implementation details, increasing leverage and locality. This Skill evaluates your existing modules to find shallow designs where complexity leaks out to many call sites instead of being contained.

You can generate an architecture review report by scanning your repository for deepening opportunities. This Skill produces a structured HTML architecture report featuring before-and-after visuals and a top recommendation for consolidating logic into deeper modules.

Yes, you can compare alternative interface designs to weigh trade-offs across module depth, locality, and seam placement. This Skill evaluates dependency categories and helps you explore design options to determine which interface creates the deepest, most testable module.

Yes, this architecture review tool uses domain language from CONTEXT.md and ADRs to evaluate your codebase. It actively flags conflicts with existing architectural decisions when proposing deepening opportunities and better seams for your modules.

You should avoid introducing adapters during refactoring unless they are fully justified by the architecture review. This Skill recommends defining better seams and consolidating logic into deeper modules first, only suggesting adapters when they genuinely resolve tight coupling and testability gaps.