map-codebase
Deep architecture report that fans out parallel inspections across different aspects of the codebase (structure, tech stack, APIs, patterns, data flow, dependencies, testing) and synthesizes findings into a comprehensive document at .turbo/codebase-map.md and .turbo/codebase-map.html. Use when the user asks to \"map the codebase\", \"map codebase\", \"architecture report\", \"codebase overview\", \"architecture overview\", \"what am I looking at\", or \"explain this codebase\".
npx skills add majiayu000/claude-skill-registry --skill map-codebase-tobihagemann-turbo-3 --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Map Codebase Deep architecture report. Fans out parallel inspections across different aspects of the codebase, synthesizes their findings, and writes `.turbo/codebase-map.md` and `.turbo/codebase-map.html`. Analysis-only. ## Task Tracking At the start, use `update_plan` to track each phase: 1. Scope 2. Launch inspection agents 3. Synthesize and generate markdown report 4. Generate HTML report ## Step 1: Scope If `$ARGUMENTS` specifies paths, use those directly (skip the question). Otherwise, use `request_user_input` to confirm scope: - **Entire codebase** — inspect everything - **Specific paths** — user provides directories or file patterns Once scope is determined, glob for source files in the selected scope. Exclude generated and vendored directories (`node_modules/`, `dist/`, `build/`, `vendor/`, `__pycache__/`, `.build/`, `DerivedData/`, `target/`, `.tox/`, and others appropriate to the project). Build a file manifest grouped by top-level source directory. This manifest is shared with all agents as a starting point. Agents may explore beyond it based on what they discover. ## Step 2: Launch Inspection Agents Launch the 7 agents below in parallel. Each agent receives the scope
- Task Tracking
- Step 1: Scope
- Step 2: Launch Inspection Agents
- Dimensions
- Step 3: Synthesize and Generate Markdown Report
- Report Template
- Step 4: Generate HTML Report
- Rules
What does the map-codebase skill do?
Deep architecture report that fans out parallel inspections across different aspects of the codebase (structure, tech stack, APIs, patterns, data flow, dependencies, testing) and synthesizes findings into a comprehensive document at .turbo/codebase-map.md and .turbo/codebase-map.html. Use when the user asks to \"map the codebase\", \"map codebase\", \"architecture report\", \"codebase overview\", \"architecture overview\", \"what am I looking at\", or \"explain this codebase\".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill map-codebase-tobihagemann-turbo-3 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.