Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
Python ai-agentsantigravityastclaude-codecode-analysiscode-searchcodexcursordeveloper-toolsgeminigraphifygraphragknowledge-graphleidenllmmcpopenclawragskillstree-sitter
README: add --watch to usage, describe --wiki in What you get
Safi546fc0b3469b
diff --git a/README.md b/README.mdindex 74ca1c6a8..978cdf8c2 100644--- a/README.md+++ b/README.md@@ -69,6 +69,7 @@ When the user types `/graphify`, invoke the Skill tool with `skill: "graphify"`/graphify path "DigestAuth" "Response"/graphify explain "SwinTransformer"+/graphify ./raw --watch # auto-update graph whenever files change/graphify ./raw --wiki # build agent-crawlable wiki (index.md + article per community)/graphify ./raw --svg # export graph.svg/graphify ./raw --graphml # export graph.graphml (Gephi, yEd)@@ -95,6 +96,8 @@ Works with any mix of file types:**Token benchmark** - printed automatically after every run. On a mixed corpus (Karpathy repos + papers + images): **71.5x** fewer tokens per query vs reading raw files.+**Wiki** (`--wiki`) - Wikipedia-style markdown articles per community and god node, with an `index.md` entry point. Point any agent at `index.md` and it can navigate the knowledge base by reading files instead of parsing JSON.+Every edge is tagged `EXTRACTED`, `INFERRED`, or `AMBIGUOUS` - you always know what was found vs guessed.## Worked examples