Skill

module-map

Produces a one-screen map of unfamiliar codebase areas: entry points, core modules, data flow, callers, hidden coupling. Readable in 15 seconds for quick orientation.

developer-tools

npx claudepluginhub rohitg00/pro-workflow --plugin pro-workflow

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Orient fast in unfamiliar code. The deliverable is a map, not a tour.

SKILL.md

Similar Skills

map

Generates high-level architecture maps of codebases: layers, modules, boundaries, data flow, and dependency directions using directory surveys and lenskit graph analysis.

7 tools

universe

zoom-out

Surfaces a compact map of surrounding modules, callers, callees, and invariants for unfamiliar code regions using fd, git grep, and ast-grep. Provides structural orientation before changes.

odin

cartographer

438

Orchestrates parallel subagents to map any codebase, creating docs/CODEBASE_MAP.md with architecture, file roles, dependencies, and navigation. Updates incrementally via git or scans.

1 file

cartographer

Stats

Stars2022

Forks192

Last CommitApr 17, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

module-map

Orient fast in unfamiliar code. The deliverable is a map, not a tour.

Deliverable

A single response containing, in this order:

One-line summary of what the area does from a caller's point of view.

Entry points — every function, route, CLI command, event handler, or cron that starts a call chain in this area. File path + symbol.

Core modules — the two to five modules that contain the real logic. One line each describing their role.

Data flow — ASCII arrows showing the dominant path for the most common input. Skip error paths unless they matter architecturally.

External callers — who outside this area calls in, and through which entry points.

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.

module-map

Orient fast in unfamiliar code. The deliverable is a map, not a tour.

Deliverable

A single response containing, in this order:

One-line summary of what the area does from a caller's point of view.
Entry points — every function, route, CLI command, event handler, or cron that starts a call chain in this area. File path + symbol.
Core modules — the two to five modules that contain the real logic. One line each describing their role.
Data flow — ASCII arrows showing the dominant path for the most common input. Skip error paths unless they matter architecturally.
External callers — who outside this area calls in, and through which entry points.
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.