architecture-review

To generate an architecture overview document, you analyze the codebase to map structure, detect design patterns, and produce an architecture_overview.md with evidence-backed findings and Mermaid diagrams.

The best way to analyze codebase structure for refactoring is to systematically map module boundaries, dependencies, and anti-patterns, producing actionable recommendations aligned to an analysis framework.

Yes, you can use architecture analysis to assess risks in a microservices codebase by evaluating quality attributes like extensibility, robustness, and maintainability across distributed service boundaries.

Codebase architecture analysis identifies design patterns and anti-patterns by systematically examining module layers and dependencies, documenting the findings with evidence traces in the generated overview document.

Architecture review works for both monoliths and microservices, assessing structural boundaries and quality attributes to deliver concrete recommendations for various codebase architectures.

An architecture overview document for planning changes should contain mapped codebase structure, detected patterns, Mermaid diagrams, evidence traces, and concrete refactor recommendations.