module-map — Claude Code skill: codebase map
The module-map skill builds a compact map of an unfamiliar codebase area, covering entry points, core modules, data flow, and callers. Use it when you need to get oriented.
MIT ★ 2,966 updated 2026-09-29
/plugin marketplace add rohitg00/pro-workflow
/plugin install pro-workflow@pro-workflowWhat module-map does
The response starts with a brief description, then lists entry points with file paths and symbols, core modules, the main data path, and callers from outside the area. It also flags hidden dependencies such as shared state or implicit call ordering. Each claim must be backed by a file path checked with grep.
The map has to fit on one screen. If the area is too large, the skill splits it into segments and asks which one to expand. It does not suggest code changes or inventory every file. Without a grep check, structural claims do not belong in the map.
What it helps with
- locate entry points in an unfamiliar part of a project
- trace the main data path from an entry point to its destination
- identify modules that hold the core logic
- spot shared state and implicit dependencies between files
Example prompts for the agent
- Map this part of the codebase; I’m not sure how it fits together.
- Show me the entry points and main data flow for this module.
- Help me get oriented: which files call into this area, and what does it depend on?
How to install module-map
1Plugin marketplace
/plugin marketplace add rohitg00/pro-workflow/plugin install pro-workflow@pro-workflowThis installs the whole pro-workflow plugin with all its skills
2Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill module-map -a claude-code3Manually: put the files in place
~/.claude/skills/module-map/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/module-map/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill module-map -a codex2Manually: put the files in place
.agents/skills/module-map/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill module-map -a cursor2Manually: put the files in place
.cursor/skills/module-map/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install rohitg00/pro-workflow skills/module-map2Manually: put the files in place
.github/skills/module-map/SKILL.md1Skills CLI (Vercel)
npx skills add rohitg00/pro-workflow --skill module-map -a gemini-cli2Platform CLI
gemini skills install https://github.com/rohitg00/pro-workflow --path skills/module-mapManually: put the files in place
.devin/skills/module-map/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about module-map
How do I install module-map in Claude Code?
Add the marketplace with /plugin marketplace add rohitg00/pro-workflow, then install the plugin with /plugin install pro-workflow@pro-workflow.
What does module-map do?
It creates a one-screen map of an area, showing entry points, core modules, data flow, external callers, and hidden dependencies. Claims must be supported by file paths checked with grep.
What happens if the code area is too large for one screen?
The skill splits it into segments and asks which one to expand. It should not silently leave out part of the codebase.
Source text
SKILL.md · MIT
--- name: module-map description: Produce a one-screen map of an unfamiliar area of the codebase: entry points, modules, data flow, callers. Designed to be read in fifteen seconds. Use when the user says "I do not know this area", "give me the map", "zoom out", "orient me". --- # module-map Orient fast in unfamiliar code. The deliverable is a map, not a tour. ## Deliverable A single response containing, in this order: 1. **One-line summary** of what the area does from a caller's point of view. 2. **Entry points** — every function, route, CLI command, event handler, or cron that starts a call chain in this area. File path + symbol. 3. **Core modules** — the two to five modules that contain the real logic. One line each describing their role. 4. **Data flow** — ASCII arrows showing the dominant path for the most common input. Skip error paths unless they matter architecturally. 5. **External callers** — who outside this area calls in, and through which entry points. 6. **Hidden coupling** — anything that looks independent but is not (shared singletons, global state, implicit ordering, undocumented contracts between files). ## Rules - Fifteen-second read target. If the map exceeds one screen, cut it. - Every claim must be backed by a file path. No remembered or inferred structure without a grep behind it. - Do not list every file. Curate. A good map omits deliberately. - Do not propose changes. Mapping is orientation; refactoring is a different skill. - If the area is too large to map in one screen, segment it and ask the user which segment to expand. Do not silently drop half the code. ## Format ``` AREA: <one-line summary> ENTRY POINTS - <path>:<symbol> — <role> CORE MODULES - <path> — <role> FLOW <entry> -> <module> -> <module> -> <sink> CALLERS - <path> — uses <entry> HIDDEN COUPLING - <description> (<path>) ``` Use the exact headers. Consistency lets the user scan.
© Rohit Ghumare · MIT · rohitg00/pro-workflow