GSD Codebase Mapper

Analyze codebase structure, dependencies, and technical debt to produce ARCHITECTURE.md and STACK.md.

Updated Aug 7, 2025
One-click install
npx skills add https://github.com/hGriff0n/velopitt --skill gsd-codebase-mapper-hgriff0n
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: GSD Codebase Mapper
Source: https://github.com/hGriff0n/velopitt/tree/main/.agent/skills/codebase-mapper
Command: npx skills add https://github.com/hGriff0n/velopitt --skill gsd-codebase-mapper-hgriff0n

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzes codebases to produce architectural context, identify patterns, and surface technical debt for planning and refactoring.

Core Features & Use Cases

  • Structure Analysis: Understand how the project is organized, entry points, tests, configuration, and asset layout.
  • Dependency Analysis: Map production and development dependencies, versions, and potential vulnerabilities.
  • Pattern Analysis: Identify naming conventions, component patterns, API surfaces, and data models.
  • Integration Analysis: Map external services, APIs, databases, and environment dependencies.
  • Technical Debt Analysis: Surface TODOs, deprecated code, and potential refactors.

Quick Start

Run the codebase mapper against a project directory to generate ARCHITECTURE.md and STACK.md.

Frequently Asked Questions about GSD Codebase Mapper

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

FAQPage Schema
How do I analyze codebase structure and identify technical debt for refactoring?

To analyze codebase structure and identify technical debt, the mapper scans source, tests, configs, and build files across common repository layouts to produce an architecture map highlighting actionable debt items.

Can I map code dependencies and external service integrations automatically?

Yes, you can map production and development dependencies, versions, external APIs, databases, and environment dependencies by scanning configuration and source files to reveal the full integration surface.

What is the best way to generate architecture documentation for an existing repository?

The best way to generate architecture documentation is to run a codebase mapper against the project directory, which deterministically outputs comprehensive ARCHITECTURE.md and STACK.md files.

How does pattern analysis work when mapping a codebase?

Pattern analysis works by scanning the codebase to identify naming conventions, component patterns, API surfaces, and data models, providing a structured view of the architectural design.

Does the codebase mapper support multiple programming languages and frameworks?

The codebase mapper applies to common repository layouts and languages, scanning source, tests, configs, and build files to support architectural planning across diverse project structures.

What types of technical debt items are surfaced during codebase analysis?

The technical debt analysis surfaces TODOs, deprecated code, and potential refactors by scanning the codebase to support planning and architectural improvements.