module-map

Generates a one-screen map of unfamiliar codebase areas covering entry points, modules, and data flow.

1|Updated May 6, 2026
One-click install
npx skills add https://github.com/surfingalien/FinSurfing --skill module-map-surfingalien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: module-map
Source: https://github.com/surfingalien/FinSurfing/tree/main/.claude/skills/module-map
Command: npx skills add https://github.com/surfingalien/FinSurfing --skill module-map-surfingalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you land in an unfamiliar part of a codebase, reading every file wastes time and produces no clear picture. This Skill produces a compact, evidence-backed map of any code area so you can orient yourself in fifteen seconds instead of an hour. ## Core Features & Use Cases - Entry Point Discovery: Lists every function, route, CLI command, event handler, or cron that starts a call chain, with file path and symbol. - Data Flow Diagram: Renders the dominant execution path as ASCII arrows from entry to sink. - Hidden Coupling Detection: Surfaces shared singletons, global state, and undocumented contracts between files that look independent but are not. - Use Case: You join a project and need to understand the billing module before a standup. Ask for the map and get entry points, core modules, callers, and coupling in one screen. ## Quick Start Ask the assistant to give you the map of the billing module so you can orient yourself before making changes.

Frequently Asked Questions about module-map

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

FAQPage Schema
How do I quickly understand an unfamiliar codebase area?

Request a module map of the area. The output lists entry points, two to five core modules, the dominant data flow as ASCII arrows, external callers, and hidden coupling, all backed by file paths and sized for a fifteen-second read.

What should a codebase orientation map include?

A useful map includes a one-line summary, entry points with file paths and symbols, core modules with one-line roles, the dominant data flow, external callers, and hidden coupling such as shared singletons or undocumented contracts.

How do I find hidden coupling between modules?

Look for shared singletons, global state, implicit ordering, and undocumented contracts between files. The map's hidden coupling section surfaces these with the file path where each dependency lives.

What happens when a code area is too large to map?

The area is segmented and you are asked which segment to expand first. The map never silently drops half the code or exceeds one screen, keeping the output scannable.

Does the module map suggest refactoring changes?

No. The map is strictly for orientation and does not propose changes. Refactoring recommendations are a separate task; the map only documents verified structure with file-path evidence.