GSD Codebase Mapper

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

Updated Feb 12, 2026

Search Tags:#architecture #documentation #codebase #dependency analysis #technical debt #mapper

Ready to run

npx skills add https://github.com/nickthelegend/molfi --skill gsd-codebase-mapper-nickthelegend

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: GSD Codebase Mapper
Source: https://github.com/nickthelegend/molfi/tree/main/.agent/skills/codebase-mapper
Command: npx skills add https://github.com/nickthelegend/molfi --skill gsd-codebase-mapper-nickthelegend

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of understanding complex codebases, identifying their structure, dependencies, and potential technical debt, enabling better planning and maintenance.

Core Features & Use Cases

Codebase Analysis: Scans project structure, dependencies, and coding patterns.
Technical Debt Identification: Surfaces TODOs, FIXMEs, and deprecated code.
Documentation Generation: Produces ARCHITECTURE.md and STACK.md files.
Use Case: Onboarding a new developer to a large, unfamiliar project by providing them with a clear architectural overview and technology stack documentation.

Quick Start

Use the GSD Codebase Mapper to analyze the current project directory and generate ARCHITECTURE.md and STACK.md files.

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 an existing codebase for structure and technical debt?▼

Analyzing an existing codebase for structure and technical debt requires traversing the file system and pattern matching to identify project dependencies, coding conventions, and deprecated code automatically.

How do I generate architecture documentation for a large software project?▼

Generating architecture documentation for a software project is done by scanning the codebase to map structural patterns and dependencies, which produces ARCHITECTURE.md and STACK.md files for onboarding and maintenance.

What is the best way to identify technical debt and deprecated code during refactoring?▼

The best way to identify technical debt during refactoring is to scan the codebase for TODOs, FIXMEs, and deprecated code patterns, surfacing maintenance issues alongside structural dependency analysis.

Can I map codebase dependencies without installing additional libraries?▼

Yes, you can map codebase dependencies without external libraries by using built-in shell commands for file system traversal and JSON parsing to identify project type and dependency structures directly.

Does codebase mapping work for project onboarding in unfamiliar software environments?▼

Codebase mapping works for project onboarding by analyzing the project directory to generate a clear architectural overview and technology stack documentation, helping new developers understand unfamiliar environments quickly.