codebase-mapper

Analyzes codebase structure, dependencies, patterns, and technical debt to generate ARCHITECTURE.md and STACK.md.

1|Updated Sep 3, 2026
One-click install
npx skills add https://github.com/amanpal3/SKILLs --skill codebase-mapper-amanpal3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-mapper
Source: https://github.com/amanpal3/SKILLs/tree/main/.agent/plugins/gsd/.agents/skills/codebase-mapper
Command: npx skills add https://github.com/amanpal3/SKILLs --skill codebase-mapper-amanpal3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When joining an unfamiliar project or planning changes to an existing codebase, developers lack a clear picture of its structure, dependencies, and hidden technical debt, making planning risky and slow. ## Core Features & Use Cases - Structure and Dependency Mapping: Scans source directories, entry points, and package manifests (package.json, requirements.txt, Cargo.toml, go.mod) to map runtime and development dependencies. - Pattern and Integration Analysis: Identifies naming conventions, API routes, state management patterns, and external services such as databases and third-party APIs. - Technical Debt Discovery: Surfaces TODOs, FIXMEs, deprecated code, missing tests, and leftover debug statements. - Use Case: Before refactoring a legacy Node.js application, run the mapper to produce ARCHITECTURE.md and STACK.md so the team can plan work based on documented components, data flow, and known debt items. ## Quick Start Ask the agent to map this codebase and generate ARCHITECTURE.md and STACK.md documenting its structure, dependencies, and technical debt.

Frequently Asked Questions about codebase-mapper

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

FAQPage Schema
How do I document an existing codebase architecture automatically?▼

Run a codebase mapping pass that scans directory structure, package manifests, and code patterns, then generates ARCHITECTURE.md and STACK.md. These files capture components, data flow, dependencies, and conventions for planning.

How to find technical debt in a legacy project?▼

Search the source tree for TODO, FIXME, HACK, and XXX markers, deprecated annotations, and leftover console debug statements. Combine this with dependency audits for outdated packages and known vulnerabilities.

What project types does codebase mapping support?▼

Project type is detected from marker files: package.json for Node.js, requirements.txt or pyproject.toml for Python, Cargo.toml for Rust, go.mod for Go, and .csproj files for .NET.

Does codebase mapping work with monorepos or large projects?▼

The scan excludes noise directories like node_modules, .git, dist, and build to keep analysis focused. Very large monorepos may require scoping the scan to individual packages for readable output.

What is the difference between ARCHITECTURE.md and STACK.md?▼

ARCHITECTURE.md documents components, data flow, integrations, conventions, and technical debt. STACK.md lists runtime versions, production and development dependencies, infrastructure services, and configuration variables.