graphify-query-craftlisted

# Graphify query craft ## When to call The crisp test from D-008's epistemological frontier: > **Structure question → Graphify.** > **Semantic question → Cognee work.** Examples of **structure** questions you should answer with a `graphify query` BEFORE reading any file: - "Who calls `process_payment`?" - "What depends on the `User` model?" - "Where is the main entry point?" - "What is the call graph for the auth flow?" - "What are the god nodes in this codebase?" - "What connects the data layer to the API?" - "Show me everything that imports `pandas`." Examples of **semantic** questions that go to Cognee work, not Graphify: - "Why was X deprecated?" → ADR in Cognee work - "What did we decide about Y last sprint?" → decision in Cognee work - "How does the team handle Z?" → runbook in Cognee work If you can't tell which side of the line you're on, prefer Graphify first — its answer is cheaper and structurally precise. Cognee work is the right second hop when the Graphify answer is structurally correct but the engineer needs the WHY. ## How to call The graphify CLI lives outside Claude Code (installed via `uv tool install "graphifyy>=0.8.33"` — pin matters: 0.8.33 fixed the test-file-orphan bug; earlier 0.8.x silently dropped test edges). It writes graphs into `<project>/graphify-out/` and the queries traverse `graphify-out/graph.json`. ```bash # First, make sure the graph is current — fast on warm cache: graphify update . # Then ask the question: graphify query "w