gsd-map-codebase

Analyze a codebase and generate structured documentation on stack, architecture, and conventions.

4|Updated Apr 11, 2026

Search Tags:#architecture #documentation #onboarding #refactoring #codebase #analysis

Ready to run

npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-map-codebase-electroheadfx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-map-codebase
Source: https://github.com/electroheadfx/efx-mux/tree/main/.codex/skills/gsd-map-codebase
Command: npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-map-codebase-electroheadfx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly understand an existing codebase by coordinating parallel analysis and turning the findings into structured project documentation.

Core Features & Use Cases

Codebase discovery: Breaks a repository into focused analysis areas so architecture, stack, quality, and risks can be captured efficiently.
Structured documentation output: Produces a consistent set of planning documents that summarize the codebase state for onboarding or refactoring.
Use Case: A developer inherits an unfamiliar project and uses this Skill to generate a complete map before planning the next implementation phase.

Quick Start

Use the gsd-map-codebase skill to analyze this repository and produce the standard codebase documentation set.

Frequently Asked Questions about gsd-map-codebase

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

FAQPage Schema

How do I map an existing codebase for onboarding documentation?▼

Codebase mapping analyzes an existing repository to produce structured documentation covering stack, architecture, conventions, testing, integrations, and concerns. It breaks the project into focused areas so architecture and risks can be captured efficiently for onboarding.

What is the best way to analyze a brownfield codebase before refactoring?▼

Pre-refactor codebase assessment requires coordinated repository inspection to capture architecture, quality, and risks. This generates a consistent set of planning documents summarizing the current codebase state for downstream implementation decisions.

Can I generate architecture documentation automatically from an unfamiliar repository?▼

Generating architecture documentation from an unfamiliar repository involves coordinated inspection to identify the stack, conventions, and concerns. This produces a standard documentation set that summarizes the project state for quick understanding.

Does codebase mapping work for pre-refactor assessment tasks?▼

Codebase mapping supports pre-refactor assessment by organizing repository inspection into focused analysis areas. It produces structured output capturing architecture, integrations, and concerns, providing a consistent baseline for planning downstream changes.

What limitations should I expect when analyzing a codebase for structured documentation?▼

Analyzing a codebase for structured documentation requires an existing repository for coordinated inspection. The task focuses on mapping the current state and generating planning documents, rather than modifying code or resolving detected concerns automatically.