GSD Codebase Mapper

Analyze codebases and generate ARCHITECTURE.md and STACK.md documentation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/0futuresystems/future-water-systems --skill gsd-codebase-mapper-0futuresystems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: GSD Codebase Mapper
Source: https://github.com/0futuresystems/future-water-systems/tree/main/.agent/skills/codebase-mapper
Command: npx skills add https://github.com/0futuresystems/future-water-systems --skill gsd-codebase-mapper-0futuresystems

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you understand the structure, dependencies, and potential issues within any codebase, making it easier to plan, maintain, and refactor your projects.

Core Features & Use Cases

  • Codebase Analysis: Scans project directories to map structure, identify patterns, and detect technical debt.
  • Documentation Generation: Produces ARCHITECTURE.md and STACK.md files for comprehensive project documentation.
  • Use Case: Onboarding a new developer to a complex legacy system by providing them with a clear map of its architecture and technology stack.

Quick Start

Use the GSD Codebase Mapper skill to analyze the current project directory and generate documentation.

Frequently Asked Questions about GSD Codebase Mapper

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

FAQPage Schema
How do I map codebase architecture and identify technical debt automatically?

To map codebase architecture and identify technical debt, this Skill scans your project directories to analyze structure, dependencies, and patterns, generating comprehensive documentation for your software engineering projects.

Can I generate architecture documentation for Node.js, Python, Rust, Go, and .NET projects?

Yes, you can generate architecture documentation for Node.js, Python, Rust, Go, and .NET projects. The Skill parses manifest files and scans source code within these environments to detect common patterns and debt indicators.

What is the best way to document a legacy codebase for new developer onboarding?

The best way to document a legacy codebase for onboarding is to scan the project directory to map its structure, dependencies, and integrations, producing clear ARCHITECTURE.md and STACK.md files for new developers.

Does codebase scanning require external dependencies to map project structure?

No, codebase scanning requires no external dependencies to map project structure. The Skill natively parses your manifest files and analyzes source code without needing additional tools or packages installed.

How do I create a STACK.md file detailing my project's technology stack?

To create a STACK.md file detailing your technology stack, the Skill analyzes your codebase by parsing manifest files and scanning source code to identify the frameworks, libraries, and patterns used in your project.

What specific technical debt indicators are detected during codebase analysis?

During codebase analysis, the Skill detects technical debt indicators by scanning source code for common patterns and structural issues, mapping them out in the generated ARCHITECTURE.md documentation to highlight areas needing refactoring.