codebase-summarizer

Run the codebase-summarizer Skill on the repository root. It recursively scans the folder tree, detects the framework from telltale config files, maps entry points, and generates an ARCHITECTURE.md with diagrams and module explanations.

An effective architecture document includes a system summary, tech stack, high-level diagram, project structure explanation, entry points, data flow diagrams, common patterns, how-to guides for frequent tasks, and a key-files reference table.

Use Mermaid graph blocks for component relationships and sequenceDiagram blocks for request lifecycles. The Skill generates these automatically by tracing requests through controllers, services, and data layers.

Yes, the Skill detects frameworks via telltale files like next.config.js, nest-cli.json, manage.py, or Cargo.toml, and locates entry points such as main.tsx, server.ts, app.py, or main.go across languages.

Generated documentation reflects static structure and may miss runtime behavior, implicit conventions, or business context known only to the team. It requires manual updates as the architecture evolves to stay accurate.