Skip to content
FunCoding

Search

Search docs, Skills and MCP

codebase-documenter

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.

代码质量与审查679productivity-skills-plugin/skills/codebase-documenter/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/mhattingpete/claude-skills-marketplace/codebase-documenter/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.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

Similar Skills

claude-api
anthropics/skills180k

claude-api

Reference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).

Code quality & review

ponytail-review
DietrichGebert/ponytail158k

ponytail-review

Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.

Code quality & review

code-review-and-quality
addyosmani/agent-skills103k

code-review-and-quality

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch. Use when asked to review a diff or a pull request, even when the diff is pasted inline.

Code quality & review

documentation-and-adrs
addyosmani/agent-skills103k

documentation-and-adrs

Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

Code quality & review

code-simplification
addyosmani/agent-skills103k

code-simplification

Simplifies code for clarity. Use when refactoring code for clarity without changing behavior. Use when code works but is harder to read, maintain, or extend than it should be. Use when reviewing code that has accumulated unnecessary complexity.

Code quality & review

understand
Egonex-AI/Understand-Anything86k

understand

Analyze a codebase to produce an interactive knowledge graph for understanding architecture, components, and relationships

Code quality & review