Skip to content

graphify (OpenCode skill)

Knowledge-graph skill for OpenCode (Graphify-Labs/graphify). Maps a project (code + docs + PDFs + media) into a queryable graph instead of grepping. /graphify . builds graphify-out/{graph.html, GRAPH_REPORT.md, graph.json}.

Install (2026-07-18)

  • Installed uv → ~/.local/bin/uv (curl astral.sh/uv/install.sh).
  • uv tool install graphifyy (v0.9.18). NOTE: PyPI package is graphifyy (double-y), command is graphify.
  • graphify install --platform opencode → skill at ~/.config/opencode/skills/graphify/ + hook plugin at ~/.opencode/plugins/graphify.js (wrong dir; system uses ~/.config/opencode).
  • FIX: added /home/dini/.opencode/plugins/graphify.js to real opencode.json plugin array alongside oh-my-opencode-slim-plugin.

IMPORTANT limitation: Liquid not supported

  • graphify's tree-sitter grammars do NOT include .liquid (Shopify Dawn theme templates).
  • Running graphify . on the LEMO dawn-theme skipped ALL 160 .liquid files ("not classified").
  • Also: docs/images need an LLM API key; --code-only avoids that but only indexes JS/JSON/tree-sitter langs.
  • Result on dawn-theme: graph covered assets/*.js (444 nodes) but NONE of the Liquid templates (main-product.liquid, spec-table.liquid, snippets) — exactly the layer you edit for LEMO.
  • Decision (2026-07-18): skip graphify for the LEMO site. Use grep / ast-grep for Liquid edits instead.
  • graphify-out/ was built then deleted; regenerate anytime with cd ~/Downloads/work/dawn-theme && graphify . --code-only.

When graphify IS useful

  • Understanding JS component interactions in a codebase (god nodes, communities, import cycles).
  • Large unfamiliar non-Liquid codebases.
  • Needs API key only for docs/PDF/media semantic pass; code-only is free + local.