graphify

Convert code, docs, papers, and images into a clustered knowledge graph with HTML, JSON, and audit report outputs.

2|3|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/spideynolove/claude-dotfiles --skill graphify-spideynolove
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graphify
Source: https://github.com/spideynolove/claude-dotfiles/tree/main/.claude-global-backup/skills/graphify
Command: npx skills add https://github.com/spideynolove/claude-dotfiles --skill graphify-spideynolove

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires graphifyy.

What problem does it solve? Understanding a new codebase, research corpus, or mixed folder of notes requires reading everything manually, and connections across documents stay invisible. Graphify turns any folder into a persistent, queryable knowledge graph with community detection and an honest audit trail showing which relationships were extracted versus inferred. ## Core Features & Use Cases - Hybrid extraction pipeline: Combines deterministic AST parsing for code with parallel LLM subagents for docs, papers, and images, with caching for incremental updates. - Community detection and analysis: Clusters the graph, labels communities, finds god nodes and surprising cross-document connections, and generates a plain-language GRAPH_REPORT.md. - Multiple export targets: Produces interactive HTML, GraphRAG-ready JSON, Obsidian vaults, SVG, GraphML, Neo4j Cypher/push, and an MCP server for live agent queries. - Use Case: Point it at an unfamiliar repository to get a navigable architecture graph before touching any code, or drop papers, tweets, and notes into a folder and query the combined concept graph weeks later without re-reading. ## Quick Start Run /graphify on the current directory to build a knowledge graph and open the generated graph.html report.

Frequently Asked Questions about graphify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a knowledge graph from a codebase or folder of documents?

Run /graphify on the target path. It detects supported files, extracts entities via AST parsing for code and parallel subagents for docs and images, then clusters the graph and writes graph.html, graph.json, and GRAPH_REPORT.md to graphify-out/.

How do I update a knowledge graph incrementally when files change?

Use /graphify <path> --update to re-extract only new or changed files. A manifest and semantic extraction cache track prior runs, so unchanged files are reused instead of reprocessed, saving tokens and time.

Can I export a knowledge graph to Neo4j or Obsidian?

Yes. Use --neo4j to generate a Cypher import file or --neo4j-push to write directly to a running Neo4j instance. Use --obsidian to generate an Obsidian vault with one note per node plus a canvas file for community layout.

What file types does graphify support for extraction?

It handles code files via AST parsing, documents and papers such as Markdown and PDF, and images via vision-based extraction. Sensitive files are skipped automatically, and unsupported corpora produce a clear 'no supported files' message.

Why did graphify produce an empty graph error?

An empty graph means extraction produced no nodes, typically because all files were skipped, the corpus contains only binaries, or extraction failed. Check that the path contains supported text, code, or image files and rerun.

How do I query an existing knowledge graph without rebuilding it?

Use /graphify query "<question>" for BFS or DFS traversal with a token budget, /graphify path to find shortest paths between concepts, or /graphify explain for a plain-language summary of a node. The --mcp flag also starts a server exposing query tools to agents.