gsd-codebase-mapper

Name: gsd-codebase-mapper
Availability: InStock
Author: cshyang

Generate structured codebase analysis documents into .planning/codebase/.

Updated Mar 15, 2026

Search Tags:#planning #architecture #documentation #codebase #analysis #conventions

Ready to run

npx skills add https://github.com/cshyang/nochore --skill gsd-codebase-mapper-cshyang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-codebase-mapper
Source: https://github.com/cshyang/nochore/tree/main/capabilities/incubator/skills/gsd/agents/codebase-mapper
Command: npx skills add https://github.com/cshyang/nochore --skill gsd-codebase-mapper-cshyang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Explores a codebase and writes structured analysis documents to support planning around architecture, conventions, and structure.

Core Features & Use Cases

Generates planning documents (STACK.md, ARCHITECTURE.md, STRUCTURE.md, CONVENTIONS.md, TESTING.md, INTEGRATIONS.md, CONCERNS.md) for a selected focus area.
Writes documents directly into .planning/codebase/ to ease orchestration.
Supports brownfield and new-codebase analyses by capturing file paths and structure.

Quick Start

Run the gsd-codebase-mapper on your repository to generate the planning documents.

Frequently Asked Questions about gsd-codebase-mapper

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

FAQPage Schema

How do I generate structured codebase analysis documents for architecture planning?▼

Generate structured codebase analysis by running this Skill on your repository; it reads the repository layout and writes STACK.md, ARCHITECTURE.md, and CONVENTIONS.md into .planning/codebase/ to support planning and governance.

What is the best way to document codebase conventions and structure for a new team?▼

Document codebase conventions and structure by generating standardized planning files like CONVENTIONS.md and STRUCTURE.md into the .planning/codebase/ directory, which eases downstream orchestration and team onboarding.

Can I analyze an existing brownfield codebase to understand its testing and integrations?▼

Yes, you can analyze a brownfield codebase to understand its testing and integrations by capturing file paths and structure, which produces TESTING.md and INTEGRATIONS.md to map existing dependencies and coverage.

Does codebase analysis for planning work with repositories of varying sizes and complexity?▼

Codebase analysis for planning supports repositories of varying sizes and complexity, applying to both brownfield and new-codebase analyses to capture file paths, structure, and architectural concerns.

What specific planning documents are generated to support architecture and governance?▼

The specific planning documents generated to support architecture and governance include STACK.md, ARCHITECTURE.md, STRUCTURE.md, CONVENTIONS.md, TESTING.md, INTEGRATIONS.md, and CONCERNS.md.