What problem does it solve? Answering codebase architecture questions by grepping raw source is slow and imprecise. This Skill routes questions about how a game's code connects — what calls what, where a node lives, how two modules relate — through a prebuilt knowledge graph, returning a scoped subgraph instead of scattered file matches. ## Core Features & Use Cases - Natural-language graph queries: Run graphify query for BFS/DFS traversal that returns a scoped answer, plus graphify path to show how two nodes relate and graphify explain for plain-language node summaries. - Graph build and refresh: Build a graph with graphify . when none exists, and refresh it cheaply with AST-only graphify update . after code changes; optional auto-refresh via a PostToolUse hook. - Use Case: While working in a Godot game project, ask "what connects to the telemetry binder?" and get a scoped subgraph answer from graphify-out/graph.json instead of manually searching dozens of GDScript files. ## Quick Start Ask the agent to use the graphify knowledge graph to explain how the data-binding module connects to the scene loader in this project.
