What problem does it solve? Understanding a large codebase or mixed corpus of documents requires reading hundreds of files manually. This Skill turns any folder into a persistent knowledge graph with community detection and an honest audit trail, so architecture questions can be answered by querying the graph instead of re-reading source files. ## Core Features & Use Cases - Knowledge graph construction: Extracts entities and relationships from code (AST-based, no LLM needed), docs, papers, images, and transcribed video, producing interactive HTML, GraphRAG-ready JSON, and a plain-language GRAPH_REPORT.md. - Graph querying: Answers natural-language questions via BFS/DFS traversal, finds shortest paths between concepts, and explains individual nodes with source citations. - Incremental updates and exports: Supports --update for changed files only, --watch for auto-rebuilds, and exports to Neo4j, FalkorDB, GraphML, SVG, Obsidian vaults, and an MCP server. - Use Case: Point it at a repository with /graphify ., then ask "How does the authentication flow reach the database?" and get an answer traced through the graph with file and line citations. ## Quick Start Run /graphify on the current directory to build the knowledge graph, then ask any question about the codebase to query it.