What problem does it solve? Understanding a large or unfamiliar codebase requires re-reading raw files repeatedly, which wastes tokens and time. This Skill guides building a queryable knowledge graph of an entire repository — code, docs, PDFs, images, and media — so an AI assistant answers questions from the graph instead of re-scanning source files. ## Core Features & Use Cases - Graph building and querying: Run /graphify . to map a repo into a NetworkX graph.json via a three-pass pipeline (local tree-sitter code parsing, faster-whisper media transcription, LLM semantic extraction), then query with /graphify query, path, and explain. - PR impact and CI integration: Triage pull requests by graph blast-radius (graphify prs --triage), install AST-only git hooks, and run headless extraction in CI with graphify extract --backend claude|gemini|ollama. - MCP serving: Expose the built graph as MCP tools (query_graph, shortest_path, get_pr_impact, and more) via python -m graphify.serve. - Use Case: Onboarding to a 200k-line monorepo — build the graph once, commit graphify-out/ to git, and ask "what connects auth to database?" using roughly 71x fewer tokens than re-reading files. ## Quick Start Ask the assistant to graphify this repository and then query what connects two modules in the code graph.