skills.rest
LuuKhoaHoc
LuuKhoaHocCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

GSD Codebase Mapper

Analyze codebases to map dependencies and generate ARCHITECTURE.md and STACK.md files.

Updated Mar 11, 2026
Search Tags:#documentation#dependency analysis#technical debt#codebase analysis#code scanning#architecture mapping
One-click install
npx skills add https://github.com/LuuKhoaHoc/erp-template --skill gsd-codebase-mapper-luukhoahoc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: GSD Codebase Mapper
Source: https://github.com/LuuKhoaHoc/erp-template/tree/main/.agent/skills/codebase-mapper
Command: npx skills add https://github.com/LuuKhoaHoc/erp-template --skill gsd-codebase-mapper-luukhoahoc

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 technical debt within any codebase, enabling better planning and maintenance.

Core Features & Use Cases

  • Codebase Analysis: Scans project structure, identifies patterns, and maps dependencies.
  • Technical Debt Identification: Surfaces TODOs, FIXMEs, deprecated code, and vulnerabilities.
  • Documentation Generation: Produces ARCHITECTURE.md and STACK.md files for clear project overviews.
  • Use Case: Before onboarding a new developer, use this Skill to generate a comprehensive map of the project's architecture and technology stack.

Quick Start

Use the GSD Codebase Mapper skill to analyze the current project directory and generate architecture 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 generate architecture documentation for an existing codebase?▼

Codebase analysis maps project structure, identifies patterns, and maps dependencies to produce ARCHITECTURE.md and STACK.md files detailing system architecture and technology stack.

What is the best way to identify technical debt across a software project?▼

Technical debt identification scans the codebase to surface TODOs, FIXMEs, deprecated code, and vulnerabilities. This process highlights areas needing maintenance before onboarding new developers or planning sprints.

Can I map dependencies and integrations automatically before refactoring?▼

Yes, you can map dependencies and integrations by scanning the project directory to understand structure. This generates documentation detailing system architecture to inform refactoring decisions.

Does codebase scanning work without specific framework dependencies?▼

Codebase scanning operates directly on the project directory to identify conventions and technology stack. It requires no external dependencies to analyze structure and generate architecture documentation.

When do I need to map codebase architecture and technology stack?▼

You need to map codebase architecture before onboarding a new developer, planning major refactoring, or assessing technical debt. It provides a comprehensive overview of system structure, dependencies, and conventions.

Related Skills

Explore More Software Engineering Skills→
alexanderopalexanderop

using-git-worktrees

Create isolated git worktrees for feature branches with safety checks.

Community
Advanced
apsulliapsulli

GSD Codebase Mapper

Analyze multi-language codebases to generate ARCHITECTURE.md and STACK.md with technical debt maps.

Community
Advanced
brainbrewlabsbrainbrewlabs
7

code-fixing

Fix code scanner, security auditor, and linter issues with verified edits and reports.

Official
Intermediate
icyzhicyzh
1

gitnexus-explorer

Index source code repositories into a knowledge graph with interactive web visualization.

Community
Advanced