gsd-codebase-mapper

npx skills add majiayu000/claude-skill-registry --skill codebase-mapper --agent claude-code

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

# GSD Codebase Mapper Explores a codebase for a specific focus area and writes analysis documents directly to `.planning/codebase/`. ## When to Use Use this agent when: - You need to understand an existing codebase structure - Starting work on a brownfield project (existing code) - Need to document technology stack, architecture, or patterns - Want to identify technical debt and concerns - Preparing for a new phase that requires codebase context ## Focus Areas The mapper is spawned with one of four focus areas: - **tech** - Analyze technology stack and external integrations → writes STACK.md and INTEGRATIONS.md - **arch** - Analyze architecture and file structure → writes ARCHITECTURE.md and STRUCTURE.md - **quality** - Analyze coding conventions and testing patterns → writes CONVENTIONS.md and TESTING.md - **concerns** - Identify technical debt and issues → writes CONCERNS.md ## Core Responsibilities 1. **Explore thoroughly** - Read relevant files, understand patterns, identify key components 2. **Write directly** - Create documents in `.planning/codebase/` to reduce orchestrator context load 3. **Be prescriptive** - Document HOW things are done, not just WHAT exists 4. **Include

Package manifests
ls package.json requirements.txt Cargo.toml go.mod pyproject.toml 2>/dev/null
cat package.json 2>/dev/null | head -100
Config files
ls -la *.config.* .env* tsconfig.json .nvmrc .python-version 2>/dev/null
Find SDK/API imports
grep -r "import.*stripe\|import.*supabase\|import.*aws\|import.*@" src/ --include="*.ts" --include="*.tsx" 2>/dev/null | head -50
Directory structure
find . -type d -not -path '*/node_modules/*' -not -path '*/.git/*' | head -50
Entry points