Codebase map
Analyze and map the current codebase structure, key files, and architecture. Use when running 'map codebase', 'analyze project', or when starting work on an unfamiliar project.From its SKILL.md
npx -y skills add skatekowski/wheee-plugin --skill codebase-mapAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, as published. Nobody here has run it
Codebase Map
Analyze the project structure and produce a comprehensive codebase overview.
Process
- Read project root files: package.json, Cargo.toml, pyproject.toml, go.mod, etc.
- Map directory structure (2 levels deep)
- Identify framework and language
- Find entry points (main, index, app, server)
- Map key architectural layers:
- Routes / API endpoints
- Data models / schemas
- Business logic / services
- Configuration / environment
- Tests
- Count files by type and estimate project size
- Check for existing documentation (README, ARCHITECTURE, CLAUDE.md)
Output Format
## Codebase Map
### Project
- Name: [name]
- Language: [lang] / Framework: [framework]
- Size: ~X files, ~Y lines
### Structure
[directory tree, 2 levels]
### Entry Points
- [file] — [purpose]
### Architecture Layers
- **Routes**: [directory/pattern]
- **Models**: [directory/pattern]
- **Services**: [directory/pattern]
- **Config**: [directory/pattern]
- **Tests**: [directory/pattern]
### Key Files
- [file] — [why it matters]
### Dependencies
- X production deps, Y dev deps
- Notable: [key libraries]