Agent skill · Documentation

map-codebase

Analyze codebase with parallel Explore agents to produce .planning/codebase/ documents. Use for brownfield project onboarding, refreshing codebase understanding after significant changes, before major refactoring, when onboarding to unfamiliar codebases, or when asked to understand codebase or analyze project structure. Creates structured documentation of stack, architecture, structure, conventions, testing, integrations, and concerns.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill map-codebase-philoserf-claude-code-setup-2 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 6 KB
Bundled scripts: none
Allowed tools: -Read-Write-Glob-Grep-Bash-Task
Path: skills/analysis/map-codebase-philoserf-claude-code-setup-2/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## Reference Files **Workflow & Process:** - [workflow.md](workflow.md) — Detailed orchestration and guidance **Core Templates** (always use): - [templates/stack.md](templates/stack.md) — STACK.md - [templates/architecture.md](templates/architecture.md) — ARCHITECTURE.md - [templates/structure.md](templates/structure.md) — STRUCTURE.md - [templates/conventions.md](templates/conventions.md) — CONVENTIONS.md **Optional Templates** (use as applicable): - [templates/testing.md](templates/testing.md) — TESTING.md (if tests exist) - [templates/integrations.md](templates/integrations.md) — INTEGRATIONS.md (if external services) - [templates/concerns.md](templates/concerns.md) — CONCERNS.md (if complex project) --- # Map Codebase Analyzes existing codebases using parallel Explore agents to produce structured documentation in `.planning/codebase/`. ## Objective Spawns multiple Explore agents to analyze different aspects of the codebase in parallel, each with fresh context. Results are structured documents in `.planning/` that provide a comprehensive map of the codebase state. **Core Output** (always generated): - `STACK.md` — Languages, frameworks, key dependencies - `ARCHITECTURE.md` — Sys

What's inside
Steps it walks through
  1. Reference Files
  2. Objective
  3. When to Use
  4. Process
  5. Step 1: Check Existing Documents
  6. Step 2: Determine Template Set
  7. Step 3: Load Project Context
  8. Step 4: Process Focus Area Argument
  9. Step 5: Spawn Parallel Explore Agents
  10. Step 5: Collect Agent Findings
  11. Step 6: Write Core Documents
  12. Step 7: Write Optional Documents (if selected)
  13. Step 8: Provide Next Steps
  14. Success Criteria
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the map-codebase skill do?

Analyze codebase with parallel Explore agents to produce .planning/codebase/ documents. Use for brownfield project onboarding, refreshing codebase understanding after significant changes, before major refactoring, when onboarding to unfamiliar codebases, or when asked to understand codebase or analyze project structure. Creates structured documentation of stack, architecture, structure, conventions, testing, integrations, and concerns.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill map-codebase-philoserf-claude-code-setup-2 --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.

Keep going