skills.rest
DojoGenesis
DojoGenesisCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

codebase-cartography

Map unfamiliar codebases into structured Markdown with directory roles and dependencies.

2|Updated Apr 8, 2026
Search Tags:#architecture#onboarding#repository-analysis#risk-analysis#dependency-graph#entry-points#codebase-mapping
One-click install
npx skills add https://github.com/DojoGenesis/gateway --skill codebase-cartography-dojogenesis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codebase-cartography
Source: https://github.com/DojoGenesis/gateway/tree/main/plugins/continuous-learning/skills/codebase-cartography
Command: npx skills add https://github.com/DojoGenesis/gateway --skill codebase-cartography-dojogenesis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maps unfamiliar codebases into a concise, navigable orientation so engineers can quickly find where to start, what depends on what, and which areas are risky or undocumented.

Core Features & Use Cases

  • Breadth-first structural survey: directory tree mapping at depth three with role classification and file counts to identify the heaviest code areas.
  • Entry point & dependency cataloging: locate application entry points, build/run commands, and produce internal and external dependency graphs highlighting circular dependencies.
  • Pattern and risk identification: summarize architectural patterns, surface fragile or complex "dragon" areas, and provide a recommended reading order for new contributors.

Quick Start

Map the repository at path ./my-repo and return a compact Markdown codebase map highlighting directory roles, entry points, dependency graph, architectural patterns, dragons, and a recommended reading order.

Frequently Asked Questions about codebase-cartography

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

FAQPage Schema
How do I map an unfamiliar codebase for onboarding?▼

Codebase mapping analyzes repository files and dependency manifests to identify directory roles, entry points, and architectural patterns. It outputs a navigable Markdown map featuring a dependency graph, risk registry, and recommended reading order for onboarding.

What is the best way to analyze repository dependencies and find circular references?▼

Repository dependency analysis catalogs internal and external dependencies from manifests to construct a dependency graph. This graph highlights circular dependencies and maps them alongside entry points, providing a concise structural overview for refactoring or debugging.

Can I generate an architectural pattern summary for a repository in any programming language?▼

Yes, codebase mapping applies to repositories in any programming language without prerequisites. It surveys directory structures and dependency manifests to identify architectural patterns and fragile areas, producing a language-agnostic Markdown map for refactoring or handoffs.

How do I identify fragile or complex areas in a codebase before refactoring?▼

Identify fragile areas by generating a dragon registry that surfaces complex, risky, or undocumented regions within the codebase. This risk identification process summarizes architectural patterns and highlights fragile areas to inform refactoring planning and debugging investigations.

Does codebase mapping work for project handoffs and debugging investigations?▼

Codebase mapping works for handoffs and debugging by producing a compact, navigable Markdown map of the repository. This map includes a directory role table, entry point catalog, dependency graph, and dragon registry to quickly orient engineers during handoffs.

Related Skills

Explore More Software Engineering Skills→
nholder88nholder88
2

draft-repo-readme

Draft a README from a repository's source files and commit history.

Community
Intermediate
xloxn69xloxn69
7

agileflow-sprint-planner

Generate a balanced Markdown sprint plan from backlog stories and team capacity.

Community
Intermediate
phuhao00phuhao00
12

code-analyst-agent

Analyze source code to identify symbols, call graphs, and architectural patterns.

Community
Intermediate
luigiinredluigiinred
1

investigate-diagram

Generate dependency diagrams from code or architecture definitions.

Community
Advanced