improve-codebase-architecture

To improve testability, you can explore your repository structure to locate tightly-coupled modules. The system organically navigates the codebase to categorize dependencies like in-process, local-substitutable, and ports & adapters, identifying architectural friction where understanding requires bouncing across many files.

Planning refactoring boundaries for shallow modules involves identifying coupling seams and producing a numbered set of deepening candidates. This approach focuses on improving testability by designing multiple radically different interface options to separate external mocks from internal layering.

Generating a refactoring RFC involves framing constraints and designing multiple interface options before drafting a GitHub issue. The system guides you through this process using an issue template to propose deepening refactors that address architectural friction.

You should use ports and adapters to support boundary-focused tests when integration seams create risk and brittle internal layering hides bugs. Categorizing dependencies into local-substitutable and external mock types helps isolate architectural friction and makes the codebase navigable.

Yes, you can use it to explore repository structure without writing tests first. It performs AI-driven codebase exploration to locate areas where understanding requires bouncing across files, producing refactoring candidates before any test implementation begins.