graphify

Convert files into a knowledge graph with community detection and HTML, JSON, and report outputs.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/harunjeylan/pi-agent --skill graphify-harunjeylan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: graphify
Source: https://github.com/harunjeylan/pi-agent/tree/main/skills/graphify
Command: npx skills add https://github.com/harunjeylan/pi-agent --skill graphify-harunjeylan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires graphifyy.

What problem does it solve? Understanding a large mixed corpus of code, documents, papers, images, and videos requires reading everything manually, and connections across files stay hidden. graphify turns any folder into a persistent, queryable knowledge graph with an honest audit trail showing which relationships were extracted versus inferred. ## Core Features & Use Cases - Multi-format extraction: Combines deterministic AST parsing for code with parallel LLM subagents for docs, papers, and images, plus Whisper transcription for video and audio files. - Community detection and analysis: Clusters the graph into labeled communities, surfaces god nodes and surprising cross-document connections, and tags every edge as EXTRACTED, INFERRED, or AMBIGUOUS with confidence scores. - Multiple outputs: Generates interactive HTML visualization, GraphRAG-ready JSON, a plain-language GRAPH_REPORT.md, plus optional Obsidian vault, wiki, SVG, GraphML, and Neo4j exports. - Use Case: Point it at an unfamiliar codebase or a research reading list to get a navigable graph showing architecture, concept clusters, and unexpected connections before you touch anything. ## 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 with a target path to extract entities and relationships from code, docs, papers, and images into a single graph. It produces an interactive HTML visualization, a GraphRAG-ready JSON file, and a plain-language report with community labels.

How does graphify extract relationships from code files?▼

Code files go through deterministic AST extraction that captures imports and structural relationships for free. Parallel LLM subagents then add semantic edges like call relationships, shared data structures, and architecture patterns that AST cannot detect.

Can graphify process video and audio files?▼

Yes, video and audio files are transcribed to text using Whisper before extraction, with a domain hint derived from the corpus to improve accuracy. The transcripts are then treated as documents, and you can select a larger Whisper model with the --whisper-model flag.

Does graphify support exporting to Neo4j or Obsidian?▼

Yes, the --neo4j flag generates a Cypher import file and --neo4j-push writes directly to a running Neo4j instance. The --obsidian flag generates a vault with one note per node plus a canvas file for structured community layout.

How do I update the graph when files change without reprocessing everything?▼

Use the --update flag for incremental runs that re-extract only new or changed files, since extraction results are cached per file. The --watch flag monitors a folder and rebuilds automatically on code changes without needing an LLM.

What are the limitations of graphify for large corpora?▼

Corpora over 2 million words or 200 files trigger a warning and require selecting a subfolder first. Graphs with more than 5000 nodes skip HTML visualization and should be explored through the Obsidian vault export instead.