gsd:map-codebase

Agent Skills › davepoon/buildwithclaude › gsd:map-codebase

gsd:map-codebase

GitHub

通过并行调度4个专用代理，自动分析代码库并生成7份结构化文档（如架构、技术栈、测试等），存入.planning/codebase/目录。适用于旧项目初始化、重构前评估或新成员上手，帮助快速掌握代码现状。

plugins/gsd/skills/map-codebase/SKILL.md davepoon/buildwithclaude

Trigger Scenarios

需要全面理解现有代码库结构时在启动新项目前分析遗留代码重大重构前评估当前代码状态新成员加入团队需要了解项目概况

Install

npx skills add davepoon/buildwithclaude --skill gsd:map-codebase -g -y

More Options

Non-standard path

npx skills add https://github.com/davepoon/buildwithclaude/tree/main/plugins/gsd/skills/map-codebase -g -y

Use without installing

npx skills use davepoon/buildwithclaude@gsd:map-codebase

指定 Agent (Claude Code)

npx skills add davepoon/buildwithclaude --skill gsd:map-codebase -a claude-code -g -y

安装 repo 全部 skill

npx skills add davepoon/buildwithclaude --all -g -y

预览 repo 内 skill

npx skills add davepoon/buildwithclaude --list

SKILL.md

Frontmatter

{
    "name": "gsd:map-codebase",
    "description": "Analyze codebase with parallel mapper agents to produce .planning\/codebase\/ documents",
    "allowed-tools": [
        "Read",
        "Bash",
        "Glob",
        "Grep",
        "Write",
        "Task"
    ],
    "argument-hint": "[optional: specific area to map, e.g., 'api' or 'auth']"
}

Analyze existing codebase using parallel gsd-codebase-mapper agents to produce structured codebase documents.

Each mapper agent explores a focus area and writes documents directly to .planning/codebase/. The orchestrator only receives confirmations, keeping context usage minimal.

Output: .planning/codebase/ folder with 7 structured documents about the codebase state.

<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/map-codebase.md </execution_context>

Focus area: $ARGUMENTS (optional - if provided, tells agents to focus on specific subsystem)

Load project state if exists: Check for .planning/STATE.md - loads context if project already initialized

This command can run:

Before /gsd:new-project (brownfield codebases) - creates codebase map first
After /gsd:new-project (greenfield codebases) - updates codebase map as code evolves
Anytime to refresh codebase understanding

<when_to_use> Use map-codebase for:

Brownfield projects before initialization (understand existing code first)
Refreshing codebase map after significant changes
Onboarding to an unfamiliar codebase
Before major refactoring (understand current state)
When STATE.md references outdated codebase info

Skip map-codebase for:

Greenfield projects with no code yet (nothing to map)
Trivial codebases (<5 files) </when_to_use>

1. Check if .planning/codebase/ already exists (offer to refresh or skip) 2. Create .planning/codebase/ directory structure 3. Spawn 4 parallel gsd-codebase-mapper agents: - Agent 1: tech focus → writes STACK.md, INTEGRATIONS.md - Agent 2: arch focus → writes ARCHITECTURE.md, STRUCTURE.md - Agent 3: quality focus → writes CONVENTIONS.md, TESTING.md - Agent 4: concerns focus → writes CONCERNS.md 4. Wait for agents to complete, collect confirmations (NOT document contents) 5. Verify all 7 documents exist with line counts 6. Commit codebase map 7. Offer next steps (typically: /gsd:new-project or /gsd:plan-phase)

<success_criteria>

.planning/codebase/ directory created
All 7 codebase documents written by mapper agents
Documents follow template structure
Parallel agents completed without errors
User knows next steps </success_criteria>

Version History

502fc01 Current 2026-07-05 15:13

Metadata

Files: 0
Version: 502fc01
Hash: 04ead59f
Indexed: 2026-07-05 15:13

gsd:map-codebase

gsd:map-codebase

Trigger Scenarios

Install

SKILL.md

Version History

Same Skill Collection