Skip to main content

gsd-map-codebase

Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents

소스 정보

저장소
davepoon/buildwithclaude
최근 소스 활동
2026년 5월 9일 09:12
감지된 SKILL.md 언어
영어
스타
3,565
포크
539

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
gsd:map-codebase
description
Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents
argument-hint
[optional: specific area to map, e.g., 'api' or 'auth']
allowed-tools
["Read","Bash","Glob","Grep","Write","Task"]
<objective> 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. </objective> <execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/map-codebase.md </execution_context> <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 </context> <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> <process> 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) </process> <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>
GitHub에서 보기