Understand codebase
Skill kimtth/agent-skill-100-lines-or-less/skills/understand-codebase
Use when: onboard onto an unfamiliar or large codebase by mapping its structure, dependencies, and business logic before editing.From its SKILL.md
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill understand-codebaseAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.6 KB, 315 tokens by cl100k_base, as published. Nobody here has run it
Goal: turn a codebase into a navigable knowledge graph you can explore, search, and explain — not a graph that just looks complex.
Use for:
- joining a large unfamiliar project and needing to know where to start
- learning how files, functions, and classes connect before changing one
- mapping code to business domains, flows, and process steps
- assessing which parts a change ripples into before committing
Workflow:
- Scan the project: detect languages and frameworks, discover every file.
- Extract structure deterministically (tree-sitter): imports, exports, function/class definitions, call sites, inheritance. Same input -> same edges every run.
- Layer in semantics (LLM): plain-English summaries, architectural layer per node (API / Service / Data / UI / Utility), business domains and flows.
- Build the graph — nodes are files/functions/classes, edges are dependencies.
- Generate guided tours ordered by dependency so the codebase is learned in the right order.
- Re-run incrementally: only re-analyze files whose fingerprint changed.
Outputs:
- structural + domain graph with nodes searchable by name and by meaning
- guided tours, layer view, and an onboarding guide for new contributors
- diff impact: which parts a current change affects
Rules:
- Keep structure deterministic; reserve the LLM for intent, summaries, and layering.
- Scope to a subdirectory for huge monorepos.
- Commit the graph so teammates skip the pipeline; refresh it on changed files.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.