codebase-mapper

Map source code into markdown documentation and Mermaid diagrams.

Updated May 8, 2026
One-click install
npx skills add https://github.com/b08x/dots --skill codebase-mapper-b08x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codebase-mapper
Source: https://github.com/b08x/dots/tree/main/.vibe/skills/codebase-mapper
Command: npx skills add https://github.com/b08x/dots --skill codebase-mapper-b08x

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires graphifyy, qmd, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of documenting a codebase, including generating structured markdown documentation and architecture diagrams.

Core Features & Use Cases

  • Codebase Documentation: Automatically generate documentation for codebases using graphify and qmd skills.
  • Architecture Diagrams: Generate Mermaid diagrams showing codebase architecture, call flows, and dependencies.
  • Documentation Prose: Follows SFL principles for clear, concise, and honest documentation.

Quick Start

Use the codebase-mapper skill to map the codebase at '/path/to/codebase'.

Frequently Asked Questions about codebase-mapper

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

FAQPage Schema
How do I automatically generate codebase documentation and architecture diagrams?

Automate codebase documentation by mapping source code to extract a knowledge graph and semantic search index, generating structured markdown documentation and Mermaid architecture diagrams.

How do I visualize codebase architecture using Mermaid diagrams?

Visualize codebase architecture by mapping source code ASTs to generate Mermaid diagrams, which illustrate call flows, component dependencies, and overall system structure.

Do I need graphify and qmd to map my source code structure?

Yes, codebase mapping requires the graphify dependency for AST-based knowledge graph extraction and the qmd dependency for building a semantic search index.

What is the best way to extract a knowledge graph from source code for documentation?

Extract a knowledge graph from source code by using AST-based parsing to map dependencies and call flows, then output the results as structured markdown and architecture diagrams.

Can I generate semantic search indexes and markdown documentation for an entire codebase?

Yes, you can generate semantic search indexes and structured markdown documentation for an entire codebase by processing source code with AST extraction and semantic search dependencies.

Are there limitations when generating architecture diagrams for large codebases?

Limitations depend on the AST-based knowledge graph extraction and semantic search indexing dependencies processing the codebase structure without timing out during diagram generation.