cartography

Generate hierarchical codemaps and track repository state in .slim/cartography.json.

1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/IndianBoy42/dot-opencode --skill cartography-indianboy42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cartography
Source: https://github.com/IndianBoy42/dot-opencode/tree/main/skills/cartography
Command: npx skills add https://github.com/IndianBoy42/dot-opencode --skill cartography-indianboy42

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Cartography helps orchestrators map and understand codebases by generating hierarchical codemaps and tracking state with .slim/cartography.json.

Core Features & Use Cases

  • Creates a repo map by selecting relevant files (using patterns and .gitignore) and generating per-folder codemap.md templates.
  • Produces .slim/cartography.json to record file and folder hashes for change detection.
  • Delegates per-folder exploration to sub-agents to fill in detailed codemaps for architecture understanding.

Quick Start

Run the cartographer's init workflow on your repository to generate the .slim/cartography.json state and empty codemap.md templates.

Frequently Asked Questions about cartography

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

FAQPage Schema
How do I generate a codemap for a large repository?

To generate a codemap for a large repository, the tool selects relevant files using include/exclude patterns and creates per-folder codemap templates. This process also tracks file hashes in a state file for change detection.

What is a repository codemap used for during onboarding?

A repository codemap is used for onboarding to document and navigate unfamiliar codebases by providing hierarchical architectural views. It helps new team members understand repository structures and folder-level logic quickly.

Does the repository mapping tool respect .gitignore patterns?

Yes, repository mapping supports .gitignore compatibility, allowing you to exclude irrelevant files from the codemap generation. You can also apply custom include and exclude patterns to refine the selected files.

How does codebase mapping handle change detection over time?

Codebase mapping handles change detection by recording file and folder hashes in a deterministic state file located at .slim/cartography.json. This allows the system to track modifications across ongoing documentation updates.

Can I use sub-agents to explore folder architecture during codemap generation?

Yes, you can delegate per-folder exploration to sub-agents to fill in detailed codemap templates. This helps generate comprehensive architectural reviews by breaking down the codebase mapping task into smaller units.

What's the best way to document an unfamiliar codebase structure?

The best way to document an unfamiliar codebase structure is to generate hierarchical codemaps with per-folder templates and track state in a dedicated JSON file. This supports architectural reviews and ongoing documentation.