codebase-documenter
Codebase Documenter generates comprehensive markdown documentation for software projects by analyzing their structure, architecture, components, and development practices. Use this skill when onboarding new developers, creating architecture documentation, explaining unfamiliar codebases, or establishing development guidelines for a project.
git clone --depth 1 https://github.com/mhattingpete/claude-skills-marketplace /tmp/codebase-documenter && cp -r /tmp/codebase-documenter/productivity-skills-plugin/skills/codebase-documenter ~/.claude/skills/codebase-documenterSKILL.md
# 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 1. **Explore** using Explore agent (thorough) 2. **Map structure** with Glob 3. **Read critical files** (README, entry points, core modules) 4. **Identify patterns** with Grep (imports, exports) 5. **Trace execution** paths 6. **Extract knowledge** from docs, comments, tests 7. **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
Execute Python code locally with marketplace API access for 90%+ token savings on bulk operations. Activates when user requests bulk operations (10+ files), complex multi-step workflows, iterative processing, or mentions efficiency/performance.
Perform bulk code refactoring operations like renaming variables/functions across files, replacing patterns, and updating API calls. Use when users request renaming identifiers, replacing deprecated code patterns, updating method calls, or making consistent changes across multiple locations.
Transfer code between files with line-based precision. Use when users request copying code from one location to another, moving functions or classes between files, extracting code blocks, or inserting code at specific line numbers.
Analyze files and get detailed metadata including size, line counts, modification times, and content statistics. Use when users request file information, statistics, or analysis without modifying files.
Generate multiple diverse solutions in parallel and select the best. Use for architecture decisions, code generation with multiple valid approaches, or creative tasks where exploring alternatives improves quality.
Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.
Stage, commit, and push git changes with conventional commit messages. Use when user wants to commit and push changes, mentions pushing to remote, or asks to save and push their work. Also activates when user says "push changes", "commit and push", "push this", "push to github", or similar git workflow requests.
Process and implement code review feedback systematically. Use when user provides reviewer comments, PR feedback, code review notes, or asks to implement suggestions from reviews.