- name
SKILL.md
技能檔案保留在發布者的儲存庫中。
在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add Ar9av/obsidian-wiki --skill code-understand -a cursor -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add Ar9av/obsidian-wiki --skill code-understand -a claude-code -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add Ar9av/obsidian-wiki --skill code-understand -a codex -y在終端機中貼上複製的指令。它會將這個 SKILL.md 安裝到對應的代理中。
npx skills add Ar9av/obsidian-wiki --skill code-understand -a grok -y在 Grok Bot 聊天中傳送複製的訊息。Bot 會從 GitHub 取得這個 SKILL.md,並加入你所有 Bot 共用的技能中。
Install this skill: https://github.com/Ar9av/obsidian-wiki/tree/HEAD/skills/code-understand來自發布者
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.
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.
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.--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.
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.file:line locations before forming an opinion
on the architecture.(file:lines) citations from the focus
map or from the source you opened — don't assert structure without a pointer to it..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.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.
>
---name: code-understanddescription: >---# skills/code-understand/SKILL.md常見問題
從發布者下載 skills/code-understand/SKILL.md,或複製路徑後開啟儲存庫。PlugMCP 只收錄這項技能,不代管檔案。
發布者將它存放在 https://github.com/Ar9av/obsidian-wiki。
Claude、Cursor、Codex 和 Grok Build 可以讀取你從發布者儲存庫加入的 SKILL.md。在聊天中傳送技能的 GitHub 資料夾連結,Grok Bot 就會安裝它。