What problem does it solve? Understanding a large codebase or mixed document corpus requires reading hundreds of files; graphify turns any folder into a persistent knowledge graph so questions about architecture, file relationships, and concepts are answered by graph traversal instead of manual searching. ## Core Features & Use Cases - Knowledge graph construction: Extracts entities and relationships from code (AST), docs, papers, images, and transcribed video, with an honest EXTRACTED/INFERRED/AMBIGUOUS audit trail. - Analysis and outputs: Community detection, god-node and surprising-connection analysis, plus interactive HTML, GraphRAG-ready JSON, GraphML, SVG, Neo4j/FalkorDB exports, Obsidian vaults, and a plain-language GRAPH_REPORT.md. - Query tools: BFS/DFS traversal queries, shortest-path between concepts, and plain-language node explanations, with incremental --update and --watch for keeping the graph current. - Use Case: Point it at a cloned GitHub repo (or several repos merged into one cross-repo graph), then ask "How does the auth flow reach the database?" and get an answer traced through the graph with source citations. ## Quick Start Run /graphify on the current project folder to build the knowledge graph, then ask a natural-language question about the codebase.