Agent skill
codebase-mapping
Automatic codebase indexing for invisible context injection. Catalogs project structure, file types, entry points, dependencies, and test layout.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/codebase-mapping-a5c-ai-babysitter
SKILL.md
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)
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?