codemap-creator

Generate structural codemaps and semantic codebase documentation from a root directory.

3|Updated Feb 2, 2026

Search Tags:#automation #architecture #documentation #codebase #codemap #code-map

Ready to run

npx skills add https://github.com/Dethon/ai-dev-flow --skill codemap-creator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: codemap-creator
Source: https://github.com/Dethon/ai-dev-flow/tree/main/skills/codemap-creator
Command: npx skills add https://github.com/Dethon/ai-dev-flow --skill codemap-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation of codemaps and semantic codebase specs to document a codebase, reducing manual effort and ensuring consistency across projects.

Core Features & Use Cases

Codemap generation (structural) and semantic codebase specs.
Outputs: docs/codebase/maps/code-map-{name}.json and docs/codebase/ STACK.md, INTEGRATIONS.md, ARCHITECTURE.md, STRUCTURE.md, CONVENTIONS.md, TESTING.md, CONCERNS.md
Use Case: Imagine you have a large monorepo; this tool produces a codemap and docs to guide development and onboarding.

Quick Start

Run the skill against your project root: /codemap-creator <root_dir> [--ignore <patterns>] [--codemap-only | --specs-only] Or with update mode: /codemap-creator --update

Frequently Asked Questions about codemap-creator

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

FAQPage Schema

How do I automatically generate codebase documentation and architecture specs?▼

To automatically generate codebase documentation and architecture specs, you can use a tool that scans your project root to produce structural codemaps and semantic specs like ARCHITECTURE.md and STACK.md, reducing manual effort and ensuring consistency across projects.

What files are included in a semantic codebase spec?▼

A semantic codebase spec typically includes STACK.md, INTEGRATIONS.md, ARCHITECTURE.md, STRUCTURE.md, CONVENTIONS.md, TESTING.md, and CONCERNS.md, all placed under the docs/codebase directory to provide comprehensive structural and functional documentation.

Can I generate codemaps for a large monorepo while ignoring certain directories?▼

Yes, you can generate codemaps for a large monorepo while ignoring certain directories by running the tool against your project root and passing ignore patterns via the command line, ensuring unwanted files are excluded from the final structural map outputs.

How do I update existing codemaps and codebase documentation after code changes?▼

To update existing codemaps and codebase documentation after code changes, you can run the tool in update mode, which refreshes the previously generated structural maps and semantic spec files to reflect the current state of your codebase.

Is it possible to generate only a structural codemap without the full semantic specs?▼

Yes, it is possible to generate only a structural codemap without the full semantic specs by using the codemap-only flag, which restricts the output to the JSON code map files placed under the docs/codebase/maps directory, skipping the markdown documentation.