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 of code, docs, papers, images, or videos into a persistent knowledge graph with community detection, so you can ask natural-language questions, trace dependency paths, and get plain-language explanations instead of reading everything yourself. ## Core Features & Use Cases - Knowledge Graph Construction: Extracts entities and relationships from code (AST-based, no LLM needed) and from docs/papers/images (semantic extraction), producing graph.json, an interactive HTML visualization, and a plain-language GRAPH_REPORT.md. - Graph Querying: Answers questions about the codebase via BFS/DFS traversal, finds shortest paths between two concepts, and explains individual nodes with source citations. - Incremental Updates & Exports: Supports --update for re-extracting only changed files, --watch for auto-rebuilds, and exports to Neo4j, FalkorDB, GraphML, SVG, Obsidian vaults, wikis, and an MCP server. - Use Case: Point it at a unfamiliar repository (or a GitHub URL) and ask "How does authentication flow through this system?" — it builds the graph once, then answers from the graph without re-reading the code. ## Quick Start Ask the assistant to run /graphify on the current directory to build a knowledge graph, then ask any question about how the codebase works.