code-analyzer

To generate architecture diagrams from source code, provide a module path for analysis. The system processes the codebase and outputs structured Markdown technical reports containing Mermaid diagrams, metrics, and executive summaries.

Yes, you can create living documentation for onboarding and technical audits automatically. By analyzing your code modules, the system generates structured technical reports with architecture diagrams that reflect your current codebase.

To generate a technical report with an executive summary, run the module analysis on your target codebase path. The output is a Markdown document featuring executive summaries, technical analysis, metrics, and Mermaid architecture diagrams.

The best way to plan refactoring using code analysis reports is to analyze specific module paths. This produces structured technical reports with module metrics and architecture diagrams, helping you identify structural dependencies and plan refactoring accurately.

Yes, the code analysis enforces read-before-write logic when generating technical reports. It strictly reads the provided module path before producing the structured Markdown documentation, ensuring accurate architecture diagrams and explicit unknowns.