codebase-mapping

Featured

Automatic codebase indexing for invisible context injection. Catalogs project structure, file types, entry points, dependencies, and test layout.

AI & Automation 1,788 stars 106 forks Updated 6 days ago MIT

Install

View on GitHub

Quality Score: 90/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
59
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

- 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)

Details

Author
a5c-ai
Repository
a5c-ai/babysitter
Created
8 months ago
Last Updated
6 days ago
Language
JavaScript
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

codebase-orientation

Maps an unfamiliar or large codebase before implementation by locating entry points, ownership, execution paths, conventions, tests, dependencies, change hotspots, and unresolved questions. Use when onboarding to a repository, scoping a cross-cutting change, preparing a handoff or reusable CodeTour, explaining a subsystem, or when the agent is guessing where behavior lives. Not for diagnosing one reproduced failure or designing a new architecture before the current system is understood.

94 Updated 2 weeks ago
thiientv
AI & Automation Listed

analyzing-codebase

Produces a verifiable technical map of a repository — stack, architecture, persistence, auth/tenancy, testing, CI/CD, and conventions — detected from actual evidence rather than assumed from the project's domain. Use when asked to "analyze this project", "understand this codebase", or before planning/implementing in an unfamiliar repo.

0 Updated 4 days ago
JavierQuinan
AI & Automation Listed

codebase-anatomy

Dissect a codebase to atomic nodes (functions, classes, symbols), wire the call/import web, tag each node's domain, and build a cross-domain overlap graph that ranks consolidation/de-duplication opportunities, then render an interactive HTML map. Use to restructure your own codebase into well-defined non-duplicative systems, OR to fully map and review an external repo (git URL / owner-repo) before adopting it. Triggers include "map this codebase", "dependency/relationship graph", "find duplication/overlap", "atomic dissection", "review this repo before I use it", and the /codeweb command.

0 Updated 4 days ago
GhostlyGawd