code-understand
Build a ranked, citation-backed focus map of a codebase — the files and symbols an architecture actually hangs on — using CodeGraph when available and a dependency-free builtin (regex AST extraction + `rg` cross-file references) otherwise. Use this any time you (the coding agent) need to orient in a
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 3475
- Лиценз
- MIT
- Последна проверка на записа
- 22.09.2026 г.
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add Ar9av/obsidian-wikiСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
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] \
[--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~5or a base branch).--backend—auto(default) uses CodeGraph when installed, falls back to the builtin extractor otherwise; forcebuiltinfor the dependency-free path, orcodegraphto require the enhanced backend (fails loudly if it's not installed rather than silently degrading).--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.