Logseq Review Workflow Eval
logseq/logseq
Compare two revisions of the Logseq logseq-review-workflow skill by running the same review prompt against isolated before and after skill snapshots, collecting both outputs, and producing a…
Map the load-bearing files, symbols, callers, and dependencies of an unfamiliar codebase before making changes.
Install Code Understand
$ npx skills add Ar9av/obsidian-wiki --skill code-understand -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Ar9av/obsidian-wiki code-understand --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.skills/code-understand .claude/skills/code-understand && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "code-understand" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/code-understand into .claude/skills/code-understand/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-understand", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/code-understandType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Ar9av/obsidian-wiki --skill code-understand -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Ar9av/obsidian-wiki code-understand --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.skills/code-understand .agents/skills/code-understand && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "code-understand" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/code-understand into .agents/skills/code-understand/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-understand", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Ar9av/obsidian-wiki --skill code-understand -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Ar9av/obsidian-wiki code-understand --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.skills/code-understand .cursor/skills/code-understand && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "code-understand" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/code-understand into .cursor/skills/code-understand/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-understand", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Ar9av/obsidian-wiki.git --path .skills/code-understand--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Ar9av/obsidian-wiki --skill code-understand -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Ar9av/obsidian-wiki code-understand --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.skills/code-understand .gemini/skills/code-understand && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "code-understand" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/code-understand into .gemini/skills/code-understand/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-understand", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Ar9av/obsidian-wiki code-understandInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Ar9av/obsidian-wiki --skill code-understand -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .github/skills && cp -r skills-src/.skills/code-understand .github/skills/code-understand && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "code-understand" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/code-understand into .github/skills/code-understand/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-understand", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Ar9av/obsidian-wiki --skill code-understand -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Ar9av/obsidian-wiki code-understand --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ar9av/obsidian-wiki.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.skills/code-understand .opencode/skills/code-understand && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "code-understand" agent skill from https://github.com/Ar9av/obsidian-wiki/tree/main/.skills/code-understand into .opencode/skills/code-understand/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "code-understand", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
code-understand- GitHub stars
- 3.5k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 600 words
- Files
- 1
- Skills in repo
- 39
- Repo updated
- First seen
- Licence
- MIT
At a glance
Map the load-bearing files, symbols, callers, and dependencies of an unfamiliar codebase before making changes.
- Works in 4 steps: Evidence type matters. When backend:… → Open what it cites, nothing else first.… → Cite it in your own output. If you… → …
- Architecture orientation
- SKILL.md covers When to reach for this, Running it, Reading the output and If CodeGraph isn't installed
- Calls npm
What it does
Code Understand is an agent skill from Ar9av/obsidian-wiki. 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.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Knowledge Management. The repository describes itself as: Framework for AI agents to build and maintain a digital brain through Obsidian wiki | Memory System for Agents. The licence is MIT.
When your agent uses it
- Architecture orientation
- Impact analysis
- What-would-break questions
- Finding callers
Example prompts
- “/code-understand”
Requirements
- Node.js
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Evidence type matters. When backend: codegraph, focus-map entries are structural
- Open what it cites, nothing else first. The focus map tells you where to read; it
- Cite it in your own output. If you explain the architecture back to the user or write
- It's a cache, not a deliverable. Never write the raw JSON or .codegraph/ into the
What it can do on your machine
Read from SKILL.md and the folder at commit 0cc5d90. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Code Understand loads about 1.1k tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 600 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Ar9av/obsidian-wiki at commit 0cc5d90, republished under its MIT licence (© Ar9av). 600 words, ~1,123 tokens.
Download SKILL.mdSave it as
.claude/skills/code-understand/SKILL.md (or your agent's skills folder).- 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] \
[--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.
Show full SKILL.md (250 more words)Show less
Reading the output
- Evidence type matters. When
backend: codegraph, focus-map entries are structural facts (real call-graph edges) — cite them directly. Whenbackend: builtin,defines/imports/changed-fileentries are facts, butrg-referenceentries are text-match evidence only — open the file and confirm before treating it as a real relationship. - Open what it cites, nothing else first. The focus map tells you where to read; it
never contains source bodies. Go read those
file:linelocations before forming an opinion on the architecture. - 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. - 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/codegraphor 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.
© Ar9av, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .skills/code-understand of Ar9av/obsidian-wiki.
Open the folder on GitHubat commit 0cc5d90
Compare with similar skills
Code Understand next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Code Understand this skillAr9av/obsidian-wiki | 3.5k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Logseq Review Workflow Evallogseq/logseq | 45k | — | ~1k | Automated safety check: Pass | AGPL-3.0 | |
| Baoyu URL To Markdownsdyckjq-lab/llm-wiki-skill | 2.5k | 2 repos | ~3.2k | Automated safety check: Pass | None | |
| Obsidian CLIAtmosphere/atmosphere | 3.8k | 13 repos | ~795 | Automated safety check: Pass | Apache-2.0 | |
| Esm Cjs Risk Scanlogseq/logseq | 45k | — | ~3.3k | Automated safety check: Pass | AGPL-3.0 | |
| Karpathy LLM WikiAstro-Han/karpathy-llm-wiki | 2.4k | — | ~3.6k | Automated safety check: Pass | MIT |
Similar skills
Baoyu URL To Markdown
sdyckjq-lab/llm-wiki-skill
Fetch any URL and convert to markdown using Chrome CDP. An agent skill from sdyckjq-lab/llm-wiki-skill.
Obsidian CLI
Atmosphere/atmosphere
Interact with Obsidian vaults using the Obsidian CLI to read, create, search, and manage notes, tasks, properties, and more.
Esm Cjs Risk Scan
logseq/logseq
Scan Logseq ClojureScript Node/Electron targets for npm module loading risks, especially ESM-only packages that may fail when loaded through js/require or shadow-cljs require-based shims.
Karpathy LLM Wiki
Astro-Han/karpathy-llm-wiki
A skill your agent uses when building or maintaining a personal LLM-powered knowledge base.
Zlibrary To Notebooklm
zstmfhy/zlibrary-to-notebooklm
自动从 Z-Library 下载书籍并上传到 Google NotebookLM。支持 PDF/EPUB 格式，自动转换，一键创建知识库。
More from Ar9av/obsidian-wiki
All 39 skills in this repoHermes History Ingest
Ar9av/obsidian-wiki
Ingest Hermes agent history into Obsidian as distilled knowledge.
Codex History Ingest
Ar9av/obsidian-wiki
Ingest Codex CLI conversation/session history into Obsidian as distilled knowledge.
Copilot History Ingest
Ar9av/obsidian-wiki
Ingest GitHub Copilot CLI/session history into Obsidian as distilled knowledge.
Obsidian Layout Adjustment
Ar9av/obsidian-wiki
Adjust the user's Obsidian visual layout with CSS snippets. An agent skill from Ar9av/obsidian-wiki.
Openclaw History Ingest
Ar9av/obsidian-wiki
Ingest OpenClaw session/history data into Obsidian as distilled knowledge.
Wiki Capture
Ar9av/obsidian-wiki
Turn the current conversation or finding into a structured permanent wiki note.
Related
Categories
Questions about Code Understand
What does Code Understand do?
Map the load-bearing files, symbols, callers, and dependencies of an unfamiliar codebase before making changes. Code Understand is an agent skill from Ar9av/obsidian-wiki. Map the load-bearing files, symbols, callers, and dependencies of an unfamiliar codebase before making changes.
When should I use Code Understand?
Code Understand fits situations like: architecture orientation; impact analysis; what-would-break questions; finding callers.
How do I install Code Understand in Claude Code?
Run `npx skills add Ar9av/obsidian-wiki --skill code-understand -a claude-code`. Or copy the skill folder (.skills/code-understand in Ar9av/obsidian-wiki) into .claude/skills/code-understand in your project. Claude Code loads it when a task matches its description.
How do I install Code Understand in Codex?
Run `npx skills add Ar9av/obsidian-wiki --skill code-understand -a codex`. Or copy the skill folder (.skills/code-understand in Ar9av/obsidian-wiki) into .agents/skills/code-understand in your project. Codex loads it when a task matches its description.
Can I use Code Understand in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Ar9av/obsidian-wiki --skill code-understand -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/code-understand, .gemini/skills/code-understand, .github/skills/code-understand and .opencode/skills/code-understand in your project.
What does Code Understand need to run?
Going by SKILL.md and its folder, Code Understand needs the command-line tools its instructions call (npm). Our summary lists: Node.js.
Does Code Understand access the network?
SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Code Understand safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Code Understand use?
Code Understand is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Code Understand use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Code Understand?
Skills that share tags, products or a category with Code Understand: Logseq Review Workflow Eval (logseq/logseq, 45k stars), Baoyu URL To Markdown (sdyckjq-lab/llm-wiki-skill, 2.5k stars), Obsidian CLI (Atmosphere/atmosphere, 3.8k stars) and Esm Cjs Risk Scan (logseq/logseq, 45k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Code Understand?
Ar9av (a GitHub user) maintains it in Ar9av/obsidian-wiki, which has 3,529 GitHub stars. The repository holds 39 skills in this directory. The repository was last updated on October 6, 2026.
Source: Ar9av/obsidian-wiki on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.