/graphify skill for Claude Code, Codex, Cursor and 20+ assistants: maps code, docs, PDFs and media into a local knowledge graph — tree-sitter AST, EXTRACTED/INFERRED edges, no vector store.
Reach for graphify when your agent burns tokens re-reading a repo to answer 'how does X connect to Y': one run writes graph.json plus a GRAPH_REPORT.md, then `graphify query`, `path` and `explain` answer from the graph, and strict mode in Claude Code redirects the session's first raw file read to it. Code extraction is free and deterministic (tree-sitter, ~40 languages, Leiden communities, zero LLM credits); docs, PDFs and video cost model tokens for the semantic pass, so a docs-heavy corpus is not free. Every edge is tagged EXTRACTED or INFERRED — trust the first, verify the second. Skip it if you want an always-on MCP code server with blast-radius tooling (code-review-graph, codebase-memory-mcp) or symbol-level edits (serena): graphify is on-demand, and the background-sync version is the paid graphify.com platform. Disclosure: StackMap's own discovery layer runs on graphify.
What teams reach for next — and why each earns a place beside graphify. Ranked by curator confidence.
🇺🇸 English | 🇨🇳 简体中文 | 🇯🇵 日本語 | 🇰🇷 한국어 | 🇩🇪 Deutsch | 🇫🇷 Français | 🇪🇸 Español | 🇮🇳 हिन्दी | 🇧🇷 Português | 🇷🇺 Русский | 🇸🇦 العربية | 🇮🇷 فارسی | 🇮🇹 Italiano | 🇵🇱 Polski | 🇳🇱 Nederlands | 🇹🇷 Türkçe | 🇺🇦 Українська | 🇻🇳 Tiếng Việt | 🇮🇩 Bahasa Indonesia | 🇸🇪 Svenska | 🇬🇷 Ελληνικά | 🇷🇴 Română | 🇨🇿 Čeština | 🇫🇮 Suomi | 🇩🇰 Dansk | 🇳🇴 Norsk | 🇭🇺 Magyar | 🇹🇭 ภาษาไทย | 🇺🇿 Oʻzbekcha | 🇹🇼 繁體中文 | 🇵🇭 Filipino | 🇮🇱 עברית
