explain-codebase

Analyzes a codebase to generate a browsable HTML architecture diagram.

1|1|Updated Nov 3, 2023
One-click install
npx skills add https://github.com/itsphurin/dotfiles --skill explain-codebase-itsphurin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: explain-codebase
Source: https://github.com/itsphurin/dotfiles/tree/main/.claude/skills/explain-codebase
Command: npx skills add https://github.com/itsphurin/dotfiles --skill explain-codebase-itsphurin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly grasp a codebase's structure, tech stack, and data flow by generating a single, browser-viewable architecture visualization.

Core Features & Use Cases

  • Automated architecture diagram that maps entry points, modules, and data flow across layers.
  • Tech-stack discovery by inspecting common project files (pyproject.toml, package.json, Cargo.toml, go.mod) and key configs.
  • Onboarding and reference: provides a visual overview to accelerate team ramp-up and code comprehension.

Quick Start

Open architecture.html in the project root to view the visualization.

Frequently Asked Questions about explain-codebase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an architecture diagram for my codebase?

To generate an architecture diagram, you investigate the codebase to analyze entry points and metadata files, outputting a browsable HTML visualization that maps components to architectural layers.

What is automated codebase visualization for onboarding?

Automated codebase visualization is the process of mapping entry points, modules, and data flow across layers to produce a browser-viewable architecture diagram for quick reference and team ramp-up.

How does codebase analysis discover a project's tech stack?

Codebase analysis discovers a tech stack by inspecting common project files like pyproject.toml, package.json, Cargo.toml, and go.mod to identify frameworks and key configurations.

Do I need a specific browser to view the generated architecture.html file?

You do not need a specific browser to view the architecture.html file; it requires only a standard browser to open and browse the generated visual overview from the project root.

What is the best way to map data flow across architectural layers?

The best way to map data flow across layers is to analyze common metadata files and entry points across languages, generating a single browsable HTML diagram reflecting the project structure.

Can I use this codebase analysis for projects across different languages?

Yes, you can use this codebase analysis for projects across different languages because it analyzes common metadata files and entry points across languages to map components to architectural layers.