SkillAgentSearch skills...

code-understand

Map the load-bearing files, symbols, callers, and dependencies of an unfamiliar codebase before making changes. Use for architecture orientation, impact analysis, what-would-break questions, or finding callers. Uses CodeGraph when available and a dependency-free builtin fallback.

Install / Use

npx skills add Ar9av/obsidian-wiki --skill code-understand

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

87/100

Supported Platforms

Universal

Tags

Our assessment of code-understand

code-understand scores 87/100 on our quality scale, 2117th of 4,698 Development & Engineering skills we index (top 46%).

Its SKILL.md is 4.5 KB long, split into 5 sections with 2 code examples: a solid amount of guidance for an agent.

With 3,485 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
16/20
Description
15/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so code-understand is actively maintained.
  • Our last check on 2026-11-02 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

code-understand compared with similar skills

All 4 of these similar skills score higher than code-understand; compare them before choosing.

SkillScoreStarsUpdatedFormat
code-understand (this skill)by Ar9av873.5k54d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install code-understand?
Run npx skills add Ar9av/obsidian-wiki --skill code-understand. The install tabs above show the steps for each supported agent.
Which AI agents does code-understand work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is code-understand safe to use?
It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is code-understand still maintained?
The repository was last updated about 2 months ago, so code-understand is actively maintained.

name: code-understand description: > Map the load-bearing files, symbols, callers, and dependencies of an unfamiliar codebase before making changes. Use for architecture orientation, impact analysis, what-would-break questions, or finding callers. Uses CodeGraph when available and a dependency-free builtin fallback.

Code Understand — On-Demand Architecture Focus Map

You are about to work in a codebase you don't fully know yet. Instead of grepping around or reading files at random, ask the local extractor for a focus map: the ranked symbols the architecture hangs on, each with a file:line citation and evidence type. Read only what it points at — this is a map, not a substitute for reading the actual code it cites.

When to reach for this

  • Before editing an unfamiliar module — see what calls it and what it calls before changing its shape.
  • The user asks "how does X work", "what's the impact of changing Y", "who else uses this function" for a codebase, not the wiki.
  • You're about to do a large refactor and want a ranked list of load-bearing files instead of reading the whole tree.
  • You already have a diff or a set of changed files and want to know their blast radius before finishing the change.

Not for: summarizing what a project does for the wiki (that's wiki-update Step 3b, which calls this same command as part of a bigger sync flow) — use this skill directly only when you need the focus map for your own immediate work, not to persist knowledge.

Running it

obsidian-wiki code-understand --project <dir> [--backend auto|builtin|codegraph|graphify] \
    [--changed <file>...] [--since <sha>] [--max-symbols N] [--pretty]
  • --project — defaults to the current directory.
  • No --changed/--since — seeds from every tracked file (full-project scan).
  • --changed <file> (repeatable) — seed from specific files you already know are relevant (e.g. files in the diff you're about to make).
  • --since <sha> — seed from everything changed since a git ref (e.g. --since HEAD~5 or a base branch).
  • --backend — auto (default) uses CodeGraph when installed, then an existing Graphify graph (graphify-out/graph.json, read only — never rebuilt), and falls back to the builtin extractor otherwise; force builtin for the dependency-free path, codegraph to require the enhanced backend (fails loudly if it's not installed rather than silently degrading), or graphify to require the Graphify graph.
  • --max-symbols — cap the focus map size (default 50); keep this small for a quick orientation pass, raise it for a thorough one.

GUARD: if the command is unavailable or errors, skip it and fall back to your normal exploration (grep/read) — this is an accelerant, not a dependency. Don't block work on it.

Reading the output

  1. Evidence type matters. When backend: codegraph, focus-map entries are structural facts (real call-graph edges) — cite them directly. When backend: builtin, defines/ imports/changed-file entries are facts, but rg-reference entries are text-match evidence only — open the file and confirm before treating it as a real relationship.
  2. Open what it cites, nothing else first. The focus map tells you where to read; it never contains source bodies. Go read those file:line locations before forming an opinion on the architecture.
  3. Cite it in your own output. If you explain the architecture back to the user or write it into a PR description/commit message, keep the (file:lines) citations from the focus map or from the source you opened — don't assert structure without a pointer to it.
  4. It's a cache, not a deliverable. Never write the raw JSON or .codegraph/ into the wiki vault, a PR description, or committed docs — it's a disposable sidecar in the project repo (git-ignored). Re-run it fresh next time rather than treating old output as durable.

If CodeGraph isn't installed

auto/builtin still work with zero setup (uses the regex AST extractor + rg). If you want the enhanced cross-file call-graph evidence and the user is fine with installing something:

npm install -g @colbymchenry/codegraph

or point CODE_UNDERSTANDING_CODEGRAPH_BIN at an existing binary. Never install without the user's go-ahead — ask first, then re-run the command.

Check obsidian-wiki doctor --project <dir> for the code-understanding.* capability lines (builtin, rg, codegraph, codegraph-index, codegraph-fresh, codegraph-gitignore) to see what's available before deciding which backend to request explicitly.

Related Skills

View on GitHub
GitHub Stars3.5k
CategoryDevelopment
Updated1mo ago
Forks345

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions