codebase-mapping
SkillFiles & storageLets your agent automatically index a codebase so it knows the project structure, entry points, dependencies, and tests.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the codebase-mapping skill
About this capability
Automatic codebase indexing for invisible context injection. Catalogs project structure, file types, entry points, dependencies, and test layout.
What this skill tells your AI
The instructions your AI receives, as published by a5c-ai/babysitter in library/methodologies/claudekit/skills/codebase-mapping/SKILL.md and read by ahel’s review.
- 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)
Signals
- GitHub stars
- 2k
- Forks
- 106
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
codebase-mapping- Source
- github.com/a5c-ai/babysitter