gsd-map-codebase

Analyze codebases with parallel mapper agents to generate structured planning documents.

1|Updated Sep 6, 2015
One-click install
npx skills add https://github.com/deerawan/dotfiles --skill gsd-map-codebase-deerawan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-map-codebase
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-map-codebase
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-map-codebase-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill reduces the time and uncertainty of understanding an unfamiliar or evolving codebase by producing structured, ready-to-use documentation of its current state.

Core Features & Use Cases

  • Parallel codebase mapping: Uses multiple focused mapper agents to cover technical, architectural, quality, and concern areas while writing results directly into .planning/codebase/.
  • Targeted refresh and brownfield support: Helps onboarding and pre-initialization analysis for brownfield projects, and refreshes documentation after meaningful changes.
  • Query modes for follow-up intelligence: Supports status, diff, and refresh-style workflows to answer “what changed?” and “what’s currently true?” questions when intelligence is enabled.

Quick Start

Run the map with: map-codebase --fast --focus tech to generate a lightweight tech-focused codebase snapshot in .planning/codebase/.

Frequently Asked Questions about gsd-map-codebase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate architecture documentation for an existing codebase?

To generate architecture documentation for an existing codebase, you can use parallel mapper agents to analyze technical, architectural, and quality areas, writing structured planning documents directly into a `.planning/codebase/` directory.

What is the best way to onboard onto a brownfield codebase quickly?

The best way to onboard onto a brownfield codebase quickly is running a targeted codebase analysis to produce structured documentation of its current state, reducing the time and uncertainty of understanding unfamiliar project structures.

Can I refresh codebase documentation after committing major refactoring changes?

Yes, you can refresh codebase documentation after major refactoring changes using query, diff, and refresh modes to update planning artifacts and answer what currently changed in the evolving project.

How do I map codebase architecture without analyzing every file in depth?

You can map codebase architecture without deep file analysis by running a fast, focus-based mode to generate a lightweight, area-specific snapshot such as a tech-focused codebase overview.

Does codebase mapping work with an existing state file?

Yes, codebase mapping supports optional state loading from an existing `.planning/STATE.md` file to provide context and continuity during codebase analysis and intelligence gathering.

What are the limitations of using parallel agents for codebase analysis?

A limitation of using parallel agents for codebase analysis is that mapping depends on reading existing code structures to generate planning artifacts, meaning it cannot infer undocumented behaviors or missing architectural conventions not present in the codebase.