codebase-mapping
Automatic codebase indexing for invisible context injection. Catalogs project structure, file types, entry points, dependencies, and test layout.
Best use case
codebase-mapping is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Automatic codebase indexing for invisible context injection. Catalogs project structure, file types, entry points, dependencies, and test layout.
Teams using codebase-mapping should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/codebase-mapping/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How codebase-mapping Compares
| Feature / Agent | codebase-mapping | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Automatic codebase indexing for invisible context injection. Catalogs project structure, file types, entry points, dependencies, and test layout.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Codebase Mapping ## Overview Auto-indexes the project structure to build a comprehensive codebase map. This map is used for invisible context injection via the UserPromptSubmit hook, providing Claude with project awareness without explicit user prompting. ## Map Contents ### Project Structure - Directory tree with depth-limited enumeration - Key file identification (entry points, configs, lock files) ### File Type Distribution - Language breakdown (TypeScript, JavaScript, Python, etc.) - Framework detection (React, Next.js, Express, etc.) ### Entry Points - Main entry files (index, main, app) - CLI entry points - API route definitions ### Module Dependencies - Import graph analysis - Package boundary mapping - Circular dependency detection ### Test Layout - Test directory structure - Test file patterns and conventions - Test framework identification ## Context Injection The codebase map is injected as invisible context during UserPromptSubmit, providing: - Project type and framework awareness - Convention awareness for code generation - Dependency awareness for import suggestions - Test pattern awareness for test generation ## When to Use - Automatically at ClaudeKit session start - When project structure changes significantly - Before research or specification tasks ## Processes Used By - `claudekit-orchestrator` (session initialization) - `claudekit-research` (context for research agents) - `claudekit-spec-workflow` (context for spec creation)
Related Skills
argument-mapping-reconstruction
Extract arguments from complex texts, identify premises, conclusions, and implicit assumptions, and create visual argument maps using Toulmin model or standard form
gis-mapping-humanities
Create spatial visualizations and geographic analyses for historical and cultural research questions using QGIS/ArcGIS
standards-alignment-mapping
Systematically map curriculum content to educational standards with vertical and horizontal alignment documentation
journey-mapping
Customer journey visualization, analysis, and experience mapping tools
value-stream-mapping
Create and analyze value stream maps with waste identification and process efficiency metrics
codebase-research
Systematic codebase exploration following the Iron Law - understand the problem before exploring code. Four phases with file-finder and web-researcher agents.
codebase-sync
Convention discovery and rule generation from codebase analysis. Scans project structure, builds search indexes, identifies patterns, and generates enforceable rules.
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.