Receber por email
← Voltar para o catálogo

gsd:map-codebase

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

3.1kestrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add davepoon/buildwithclaude

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/gsd-map-codebase/svg)](https://www.skillteca.com.br/skills/gsd-map-codebase)

Skills relacionadas

Ver todas de Documentos →

Alerta por categoria

Receba novas skills de Documentos toda segunda

1 email curto, só com as skills novas de Documentos. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

<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:
  4. Agent 1: tech focus → writes STACK.md, INTEGRATIONS.md
  5. Agent 2: arch focus → writes ARCHITECTURE.md, STRUCTURE.md
  6. Agent 3: quality focus → writes CONVENTIONS.md, TESTING.md
  7. Agent 4: concerns focus → writes CONCERNS.md
  8. Wait for agents to complete, collect confirmations (NOT document contents)
  9. Verify all 7 documents exist with line counts
  10. Commit codebase map
  11. 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>

Compartilhar X LinkedIn