SKILL37codebase-intelligence
Mapping Existing Codebase Structure
Builds a traceable current-state map of entrypoints, modules, responsibilities, boundaries, and dependency direction without proposing a redesign.
Primary benefit
Replaces architectural guesswork with a scoped structural map whose claims point back to concrete code and configuration evidence.When to use
Use when you need to understand how an existing codebase is organized, where execution enters, how modules divide responsibility, or which ownership boundaries are observable before another engineering decision.
When not to use
Do not use to choose a future architecture or design new boundaries; Architecture & Engineering owns those decisions through choosing-application-architecture and designing-software-boundaries.
Use cases
Orient work in an unfamiliar repository by locating entrypoints, module responsibilities, dependency direction, and ownership signals
Document the current structural seams around a capability before handing evidence to architecture or change planning
Example prompts
Use mapping-existing-codebase-structure to map the current entrypoints, modules, boundaries, dependency direction, and evidence gaps for this capability. Mark every material claim as observed, inferred, or unresolved and cite its source and location.Install this skill
Choose the command for your operating system and run it from the repository root.
Bash
./install.sh --skill mapping-existing-codebase-structurePowerShell
./install.ps1 --skill mapping-existing-codebase-structureChatGPT
Download Skill ZIPCompatibility
- Surfaces
- ChatGPT · Codex · Claude Code
- Operating systems
- Linux · macOS · Windows
- Install modes
- PluginFilesystem
Dependencies
No external dependencies
Part of systems
Curated systems that canonically include this method.
Used in evidence
Reports that explicitly list this method among the applied methods.