← ClaudeAtlas

graphifylisted

EXPLICIT INVOCATION ONLY via /graphify. Build a knowledge graph from a codebase or document corpus. Do not auto-trigger, do not suggest, do not invoke proactively. Only run when the user types /graphify.
datasci-iopsy/anaiis-dotfiles · ★ 0 · Data & Documents · score 65
Install: claude install-skill datasci-iopsy/anaiis-dotfiles
# /graphify Turn any folder of files into a navigable knowledge graph with community detection, an honest audit trail, and three outputs: interactive HTML, GraphRAG-ready JSON, and a plain-language GRAPH_REPORT.md. ## What graphify is for graphify is built around Andrej Karpathy's /raw folder workflow: drop anything into a folder (papers, tweets, screenshots, code, notes) and get a structured knowledge graph that shows you what you did not know was connected. Three things it does that Claude alone cannot: 1. **Persistent graph**: relationships are stored in `graphify-out/graph.json` and survive across sessions. 2. **Honest audit trail**: every edge is tagged EXTRACTED, INFERRED, or AMBIGUOUS. 3. **Cross-document surprise**: community detection finds connections between concepts in different files that you would never think to ask about directly. **Supported file types (parsed by tree-sitter AST):** Python, JavaScript, TypeScript, Go, Rust, Java, C, C++, Ruby, C#, Kotlin, Scala, PHP. Plus: Markdown, plain text, PDFs, and images (via Claude vision). **Not supported:** SQL, YAML, JSON, shell scripts, and other file types not listed above. If the target directory is primarily SQL (e.g. a dbt project), stop and tell the user: "graphify does not parse SQL. For dbt model dependencies, use the dbt manifest.json instead." ## Usage ``` /graphify # full pipeline on current directory /graphify <path>