codebase-mapping
FeaturedAutomatic codebase indexing for invisible context injection. Catalogs project structure, file types, entry points, dependencies, and test layout.
Install
Quality Score: 90/100
Skill Content
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
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.
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.
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.