codebase-documenter
Generates comprehensive documentation for any codebase to explain architecture, data flow, and project guidelines.
Install
mkdir -p .claude/skills/codebase-documenter && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2920" && unzip -o skill.zip -d .claude/skills/codebase-documenter && rm skill.zipInstalls to .claude/skills/codebase-documenter
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Generates comprehensive documentation explaining how a codebase works, including architecture, key components, data flow, and development guidelines. Use when user wants to understand unfamiliar code, create onboarding docs, document architecture, or explain how the system works.Key capabilities
- →Generates Mermaid diagrams for visual architecture
- →Extracts key logic from comments and documentation headers
- →Maps project directory purpose and naming conventions
- →Traces execution flow from entry points to core modules
How it works
It maps the directory structure using glob patterns, reads entry points and core modules to identify design patterns, and extracts metadata from comments and existing docs.
Inputs & outputs
When to use codebase-documenter
- →Generate an onboarding doc for new developers
- →Explain the system architecture
- →Create a high-level codebase overview
- →Document API and database schemas
About this skill
Codebase Documenter
Generates comprehensive documentation for codebases - architecture, components, data flow, development guidelines.
When to Use
- "explain this codebase"
- "document the architecture"
- "how does this code work"
- "create developer documentation"
- "generate codebase overview"
- "create onboarding docs"
What It Documents
1. Project Overview
- Purpose & vision
- Target users
- Key features
- Technology stack
- Project status
2. Architecture
- High-level structure
- Design patterns
- Data flow
- Control flow
- Diagrams (Mermaid)
- Architectural decisions
3. Directory Structure
- Organization purpose
- Naming conventions
- Entry points
- Core modules
- Configuration locations
4. Key Components
- Major modules
- Classes & functions
- Responsibilities
- Interactions
- Extension points
- Code examples
5. External Integrations
- APIs consumed
- Databases & schemas
- Authentication
- Caching
- Message queues
- File storage
6. Data Models
- Database schema
- Data structures
- Validation
- Migrations
- Data transformations
7. Development Setup
- Prerequisites
- Installation steps
- Configuration
- Running the app
- Testing
- Debugging
- Troubleshooting
8. Development Guidelines
- Coding conventions
- Testing approach
- Error handling
- Logging
- Security practices
- Performance patterns
9. Deployment
- Build process
- Deployment steps
- Environments
- Monitoring
- Rollback procedures
10. Contributing
- Development workflow
- Code review guidelines
- Testing requirements
- Documentation updates
Approach
- Explore using Explore agent (thorough)
- Map structure with Glob
- Read critical files (README, entry points, core modules)
- Identify patterns with Grep (imports, exports)
- Trace execution paths
- Extract knowledge from docs, comments, tests
- Synthesize into cohesive documentation
Output
Creates markdown documentation:
docs/
├── README.md # Overview and quick start
├── ARCHITECTURE.md # System architecture
├── DEVELOPMENT.md # Development guide
├── API.md # API documentation
├── DEPLOYMENT.md # Deployment guide
└── CONTRIBUTING.md # Contribution guidelines
Or single comprehensive doc if preferred.
Depth Levels
- Quick: High-level overview (15-30 min)
- Standard: Comprehensive coverage (30-60 min)
- Deep: Exhaustive with examples (60+ min)
Visual Elements
- Mermaid diagrams (architecture, flow charts, sequence)
- Code examples from codebase
- Specific file:line references
- Tables for structured info
- Lists for guidelines
Tools Used
- Task (Explore agent): Codebase exploration
- Glob: Map directory structure
- Grep: Find patterns, imports, exports
- Read: Analyze key files
- Write: Create documentation
- Bash: Extract metadata (git log, versions)
Success Criteria
- Complete coverage of all areas
- Clear explanations with examples
- Visual diagrams for complex concepts
- Specific file:line references
- Actionable setup/development instructions
- New developer can onboard using only docs
- Organized, navigable structure
- Accurate and current information
Integration
- code-auditor: Includes quality/security context
- project-bootstrapper: Documents bootstrap decisions
- visual-html-creator: Create visual diagrams
When not to use it
- →On non-code projects like documentation-only repositories
- →When codebase is too small to require architectural mapping
Limitations
- →Documentation accuracy depends entirely on existing code comments
- →Cannot explain proprietary binaries or compiled dependencies
How it compares
Unlike a generic prompt that hallucinates summaries, this uses iterative exploration to extract facts directly from the live file system.
Compared to similar skills
codebase-documenter side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| codebase-documenter (this skill) | 6 | 9mo | No flags | Beginner |
| c4-architecture-c4-architecture | 1 | 3mo | Review | Advanced |
| code-documentation-doc-generate | 1 | 3mo | No flags | Intermediate |
| documentation-audit | 0 | 1mo | Review | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by mhattingpete
View all by mhattingpete →You might also like
c4-architecture-c4-architecture
sickn33
Generate comprehensive C4 architecture documentation for an existing repository/codebase using a bottom-up analysis approach.
code-documentation-doc-generate
sickn33
You are a documentation expert specializing in creating comprehensive, maintainable documentation from code. Generate API docs, architecture diagrams, user guides, and technical references using AI-powered analysis and industry best practices.
documentation-audit
SatoryKono
Full audit and update of BioETL project documentation for v5.23+. Use when asked to review docs for staleness, reconcile docs with code, sync RULES.md and REQUIREMENTS.md, update architecture/provider/contract docs, reflect ADR-010/ADR-014/ADR-017, or identify dead documentation.
deepwiki-rs
sopaco
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation. Use when Claude needs to analyze source code, understand software architecture, generate technical specs, or create professional documentation from any programming language.
specification-architect
adrianpuiu
A rigorous, traceability-first system that generates five interconnected architectural documents (blueprint.md, requirements.md, design.md, tasks.md, and validation.md) with complete requirements-to-implementation traceability. Use this skill when users need to architect systems, create technical specifications, or develop structured project documentation with guaranteed traceability.
business-analyst-authority
ahmedemad3
Act as a Principal Business Analyst (8+ years exp) bridging the gap between Strategy and Execution. Specializes in translating vague vision into rigorous technical specifications using Gherkin (BDD), BPMN 2.0, and strict Requirement Engineering standards.