repo-architecture-analyst

To analyze a local repository, this skill reads the codebase from the local filesystem to extract core scenarios and map architectural decisions. It generates a long-form Markdown document detailing problem-solution mappings and visualizing flows with Mermaid diagrams.

Scenario-driven repository analysis is a technique that maps core technical challenges to their architectural decisions within a codebase. You need it when you want to turn raw repository structure into a structured, reusable design narrative for solution architecture documentation.

You can generate Mermaid diagrams from an existing codebase by running this skill on the local repository path. It visualizes architectural flows and problem-solution mappings automatically, embedding the diagrams within a comprehensive Markdown analysis document.

Yes, you can use this skill to document architectural decisions and trade-offs for a local codebase. It produces a ready-to-edit template that explains problem-solution mappings and provides a reusable format for future repository architecture analyses and decision records.

No, repository architecture analysis using this skill requires no external dependencies or components. It operates directly on the local filesystem and outputs a long-form Markdown analysis with suggested improvements, requiring only the local repository path to trigger the workflow.

The primary limitation of this codebase architecture analysis is that it requires direct access to the local filesystem and cannot analyze remote repositories directly. Additionally, while it suggests improvements and provides a design narrative, the output is a ready-to-edit template requiring human review for final architectural documentation.