graphifylisted

# graphify: query a code graph instead of re-reading files **Platform: Windows / PowerShell CLI edition.** The `graphify` invocations below are shell-neutral and run unchanged under PowerShell; the preflight and the file-locking note are Windows-specific. The Linux sibling is `graphify-cowork`. graphify parses a repo with tree-sitter into nodes (functions, classes, files) and edges (`calls`, `imports`, ...), each tagged `EXTRACTED` (explicit in source) or `INFERRED` (derived). Build once, then traverse. ## Preflight ```powershell Get-Command graphify -ErrorAction SilentlyContinue ``` If that prints nothing, **stop and use `grep` / bounded `Read` for this task.** Do not install mid-task. Tell the user the one-time fix: `uv tool install --with watchdog graphifyy`. On Windows uv installs to `%USERPROFILE%\.local\bin`, which is not always on `PATH` in a non-login shell. `--with watchdog` is required if `watch` will be used. `scoop` is irrelevant - graphify is a uv/pip package. ## Pick the command before you build anything | Question | Command | |---|---| | "how does A reach B", "is there a route from X to Y" | `graphify path "A" "B"` - **the only thing grep cannot do at any price** (2-hop answer: 253 B / ~183 tok; via grep: 3+ rounds and you must guess the middle hop) | | "what calls X", "what breaks if I change X" | `graphify affected "X()"` - 291 B / ~193 tok, directional, `file:line`, no truncation. Beats `grep -rn` (848 B / ~332 tok) on cost *and* precision | | "what i