map-codebase

Orchestrates parallel agents to generate seven MD documents in .gsd/child/.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/NAinfini/Guild_Management --skill map-codebase
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: map-codebase
Source: https://github.com/NAinfini/Guild_Management/tree/main/.kilocode/skills/map-codebase
Command: npx skills add https://github.com/NAinfini/Guild_Management --skill map-codebase

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates mapping a codebase by orchestrating parallel codebase mapper agents to generate structured documentation, enabling teams to quickly understand architecture, tech stack, and conventions across large repos.

Core Features & Use Cases

  • Orchestrates independent mapper agents to analyze codebase areas (tech, architecture, quality, and concerns) in parallel.
  • Writes 7 structured documents to .gsd/codebase/: STACK.md, INTEGRATIONS.md, ARCHITECTURE.md, STRUCTURE.md, CONVENTIONS.md, TESTING.md, and CONCERNS.md.
  • Produces a concise orchestration summary while ensuring agents operate with fresh context and without leaking intermediate results.

Quick Start

Spawn four gsd-codebase-mapper agents focused on tech, architecture, quality, and concerns, then monitor confirmations, verify the output docs, and commit the 7 generated files.

Frequently Asked Questions about map-codebase

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

FAQPage Schema
How do I generate structured documentation for a large codebase automatically?

You can generate structured codebase documentation by orchestrating parallel mapper agents to analyze your repository and output 7 markdown files covering STACK, ARCHITECTURE, STRUCTURE, CONVENTIONS, TESTING, INTEGRATIONS, and CONCERNS.

What is the best way to analyze a legacy codebase architecture and tech stack?

Analyzing a legacy codebase architecture is best handled by spawning independent agents to map tech, architecture, quality, and concerns in parallel, writing structured docs into a dedicated directory.

Does parallel codebase mapping work for monorepos?

Yes, parallel codebase mapping works for monorepos. The orchestration approach applies to software repositories of any size, including monorepos and legacy codebases needing explicit architecture and structure documentation.

What files do I need to document codebase conventions and testing?

To document codebase conventions and testing, the mapping process writes CONVENTIONS.md and TESTING.md files into the .gsd/codebase/ directory alongside STACK, ARCHITECTURE, STRUCTURE, INTEGRATIONS, and CONCERNS docs.

How do codebase mapper agents handle context transfer?

Codebase mapper agents handle context transfer by remaining minimal. The orchestrator produces a concise summary while ensuring agents operate with fresh context without leaking intermediate results.

What are the limitations of automated codebase documentation generation?

Automated codebase documentation generation requires spawning four specific mapper agents focused on tech, architecture, quality, and concerns, and you must manually verify the output docs and commit the generated files.