pelizzai-improving-architecture

To identify architectural debt, you analyze codebase evidence like recurring bugs, scattered changes, and dependency cycles. This diagnostic process pinpoints structural bottlenecks and synthesizes actionable refactoring candidates without modifying any files.

Evidence-based architectural review is a read-only health check that analyzes project history, ADRs, and source code. It categorizes findings into Strong, Worth exploring, or Speculative classes to ensure decisions are grounded in real evidence rather than aesthetic preference.

Perform a proactive architectural health check by invoking a diagnostic tool against your project. It requires access to project history, ADRs, and source code to evaluate recurring development patterns and output prioritized recommendations for maintainability.

No, architectural codebase analysis operates strictly as a read-only diagnostic tool. It synthesizes actionable refactoring candidates by evaluating codebase evidence and structural friction, ensuring your source files remain completely unmodified during the health check.

Run architectural debt analysis periodically to perform comprehensive health checks and prevent silent degradation of software architecture. This timing ensures your codebase remains maintainable and catches structural friction before it accumulates into significant technical debt.