← ClaudeAtlas

graphifylisted

Use to orient in an unfamiliar codebase with graphify, a local tree-sitter code graph — "what does this symbol touch", "how do these two connect", "trace this call chain". Opt-in (the human installs graphify once). A forward-orientation aid, NOT a reliable reverse-dependency tool. Shipped and kept current by Loom.
DanielC000/loom · ★ 6 · AI & Automation · score 78
Install: claude install-skill DanielC000/loom
# graphify `graphify` builds a **local, code-only call graph** with tree-sitter — no API key, no LLM backend, no token cost. Use it as a **forward-orientation aid**: given a symbol, see what it calls and how two symbols connect. It is fast and accurate for that. **The one thing to internalize:** graphify is strong going *forward* (`explain` / `path`) and **unreliable going backward** (`affected` — "what breaks if I change X"). Treat forward queries as trustworthy orientation and reverse queries as a lead to confirm with grep — never as ground truth. ## Setup (opt-in — assume it's present) One-time, human-installed like any host tool: `uv tool install graphifyy` (or `pipx install graphifyy`, or `pip install graphifyy`). This skill assumes it's already there. If `graphify` isn't on PATH, say so and fall back to grep/Read — don't try to install it yourself. ## Build the graph (code-only) ``` graphify update <dir> ``` Point `<dir>` at your source root (e.g. `src`). This writes `<dir>/graphify-out/graph.json`. **Only ever use `update`.** Never run `extract` or point it at a semantic/LLM backend, and never pass an API key — code-only keeps it free and local. Rebuild after substantial code changes; the graph is a snapshot. ## Use it — forward orientation (the strength) Pass `--graph <dir>/graphify-out/graph.json` to each query. - **`graphify explain "<Symbol>"`** — what this symbol touches: its outgoing calls and immediate neighbors. The go-to "what does this do / what d