docs(skills): cover maintenance commands and verification

graphify/skill-agents.md

@@ -689,6 +689,18 @@ Before traversal, expand the question against the graph's own vocabulary so a wo
 
 ---
 
+## For /graphify affected
+
+When the user asks for a change's blast radius or "what calls/depends on X?", use `graphify affected "X"` rather than a broad `query`. It reverse-traverses the graph from X and reports the callers and dependents that a change could impact. For relation/depth filters and the exact workflow, see `references/query.md`.
+
+---
+
+## Less-common maintenance commands
+
+Use these only when the request calls for them: `graphify tree` writes a collapsible hierarchy view; `graphify global add|remove|list|path` manages the cross-repository graph; `graphify check-update <path>` is the cron-safe stale-graph check; `graphify diagnose multigraph` reports same-endpoint edge-collapse risk; and `graphify merge-driver <base> <current> <other>` is for a Git merge-driver invocation. Run `graphify --help` before supplying flags, and do not substitute these commands for the normal build/query workflow.
+
+---
+
 ## For /graphify add and --watch
 
 Neither is part of the default build. When the user runs `/graphify add <url>` to fetch a URL into the corpus, or passes `--watch` to auto-rebuild on file changes, see `references/add-watch.md`.

graphify/skill-amp.md

@@ -689,6 +689,18 @@ Before traversal, expand the question against the graph's own vocabulary so a wo
 
 ---
 
+## For /graphify affected
+
+When the user asks for a change's blast radius or "what calls/depends on X?", use `graphify affected "X"` rather than a broad `query`. It reverse-traverses the graph from X and reports the callers and dependents that a change could impact. For relation/depth filters and the exact workflow, see `references/query.md`.
+
+---
+
+## Less-common maintenance commands
+
+Use these only when the request calls for them: `graphify tree` writes a collapsible hierarchy view; `graphify global add|remove|list|path` manages the cross-repository graph; `graphify check-update <path>` is the cron-safe stale-graph check; `graphify diagnose multigraph` reports same-endpoint edge-collapse risk; and `graphify merge-driver <base> <current> <other>` is for a Git merge-driver invocation. Run `graphify --help` before supplying flags, and do not substitute these commands for the normal build/query workflow.
+
+---
+
 ## For /graphify add and --watch
 
 Neither is part of the default build. When the user runs `/graphify add <url>` to fetch a URL into the corpus, or passes `--watch` to auto-rebuild on file changes, see `references/add-watch.md`.

graphify/skill-claw.md

@@ -692,6 +692,18 @@ Before traversal, expand the question against the graph's own vocabulary so a wo
 
 ---
 
+## For /graphify affected
+
+When the user asks for a change's blast radius or "what calls/depends on X?", use `graphify affected "X"` rather than a broad `query`. It reverse-traverses the graph from X and reports the callers and dependents that a change could impact. For relation/depth filters and the exact workflow, see `references/query.md`.
+
+---
+
+## Less-common maintenance commands
+
+Use these only when the request calls for them: `graphify tree` writes a collapsible hierarchy view; `graphify global add|remove|list|path` manages the cross-repository graph; `graphify check-update <path>` is the cron-safe stale-graph check; `graphify diagnose multigraph` reports same-endpoint edge-collapse risk; and `graphify merge-driver <base> <current> <other>` is for a Git merge-driver invocation. Run `graphify --help` before supplying flags, and do not substitute these commands for the normal build/query workflow.
+
+---
+
 ## For /graphify add and --watch
 
 Neither is part of the default build. When the user runs `/graphify add <url>` to fetch a URL into the corpus, or passes `--watch` to auto-rebuild on file changes, see `references/add-watch.md`.

graphify/skill-codex.md

@@ -689,6 +689,18 @@ Before traversal, expand the question against the graph's own vocabulary so a wo
 
 ---
 
+## For /graphify affected
+
+When the user asks for a change's blast radius or "what calls/depends on X?", use `graphify affected "X"` rather than a broad `query`. It reverse-traverses the graph from X and reports the callers and dependents that a change could impact. For relation/depth filters and the exact workflow, see `references/query.md`.
+
+---
+
+## Less-common maintenance commands
+
+Use these only when the request calls for them: `graphify tree` writes a collapsible hierarchy view; `graphify global add|remove|list|path` manages the cross-repository graph; `graphify check-update <path>` is the cron-safe stale-graph check; `graphify diagnose multigraph` reports same-endpoint edge-collapse risk; and `graphify merge-driver <base> <current> <other>` is for a Git merge-driver invocation. Run `graphify --help` before supplying flags, and do not substitute these commands for the normal build/query workflow.
+
+---
+
 ## For /graphify add and --watch
 
 Neither is part of the default build. When the user runs `/graphify add <url>` to fetch a URL into the corpus, or passes `--watch` to auto-rebuild on file changes, see `references/add-watch.md`.

graphify/skill-copilot.md

@@ -692,6 +692,18 @@ Before traversal, expand the question against the graph's own vocabulary so a wo
 
 ---
 
+## For /graphify affected
+
+When the user asks for a change's blast radius or "what calls/depends on X?", use `graphify affected "X"` rather than a broad `query`. It reverse-traverses the graph from X and reports the callers and dependents that a change could impact. For relation/depth filters and the exact workflow, see `references/query.md`.
+
+---
+
+## Less-common maintenance commands
+
+Use these only when the request calls for them: `graphify tree` writes a collapsible hierarchy view; `graphify global add|remove|list|path` manages the cross-repository graph; `graphify check-update <path>` is the cron-safe stale-graph check; `graphify diagnose multigraph` reports same-endpoint edge-collapse risk; and `graphify merge-driver <base> <current> <other>` is for a Git merge-driver invocation. Run `graphify --help` before supplying flags, and do not substitute these commands for the normal build/query workflow.
+
+---
+
 ## For /graphify add and --watch
 
 Neither is part of the default build. When the user runs `/graphify add <url>` to fetch a URL into the corpus, or passes `--watch` to auto-rebuild on file changes, see `references/add-watch.md`.

graphify/skill-droid.md

@@ -689,6 +689,18 @@ Before traversal, expand the question against the graph's own vocabulary so a wo
 
 ---
 
+## For /graphify affected
+
+When the user asks for a change's blast radius or "what calls/depends on X?", use `graphify affected "X"` rather than a broad `query`. It reverse-traverses the graph from X and reports the callers and dependents that a change could impact. For relation/depth filters and the exact workflow, see `references/query.md`.
+
+---
+
+## Less-common maintenance commands
+
+Use these only when the request calls for them: `graphify tree` writes a collapsible hierarchy view; `graphify global add|remove|list|path` manages the cross-repository graph; `graphify check-update <path>` is the cron-safe stale-graph check; `graphify diagnose multigraph` reports same-endpoint edge-collapse risk; and `graphify merge-driver <base> <current> <other>` is for a Git merge-driver invocation. Run `graphify --help` before supplying flags, and do not substitute these commands for the normal build/query workflow.
+
+---
+
 ## For /graphify add and --watch
 
 Neither is part of the default build. When the user runs `/graphify add <url>` to fetch a URL into the corpus, or passes `--watch` to auto-rebuild on file changes, see `references/add-watch.md`.

graphify/skill-kilo.md

@@ -692,6 +692,18 @@ Before traversal, expand the question against the graph's own vocabulary so a wo
 
 ---
 
+## For /graphify affected
+
+When the user asks for a change's blast radius or "what calls/depends on X?", use `graphify affected "X"` rather than a broad `query`. It reverse-traverses the graph from X and reports the callers and dependents that a change could impact. For relation/depth filters and the exact workflow, see `references/query.md`.
+
+---
+
+## Less-common maintenance commands
+
+Use these only when the request calls for them: `graphify tree` writes a collapsible hierarchy view; `graphify global add|remove|list|path` manages the cross-repository graph; `graphify check-update <path>` is the cron-safe stale-graph check; `graphify diagnose multigraph` reports same-endpoint edge-collapse risk; and `graphify merge-driver <base> <current> <other>` is for a Git merge-driver invocation. Run `graphify --help` before supplying flags, and do not substitute these commands for the normal build/query workflow.
+
+---
+
 ## For /graphify add and --watch
 
 Neither is part of the default build. When the user runs `/graphify add <url>` to fetch a URL into the corpus, or passes `--watch` to auto-rebuild on file changes, see `references/add-watch.md`.

graphify/skill-kiro.md

@@ -692,6 +692,18 @@ Before traversal, expand the question against the graph's own vocabulary so a wo
 
 ---
 
+## For /graphify affected
+
+When the user asks for a change's blast radius or "what calls/depends on X?", use `graphify affected "X"` rather than a broad `query`. It reverse-traverses the graph from X and reports the callers and dependents that a change could impact. For relation/depth filters and the exact workflow, see `references/query.md`.
+
+---
+
+## Less-common maintenance commands
+
+Use these only when the request calls for them: `graphify tree` writes a collapsible hierarchy view; `graphify global add|remove|list|path` manages the cross-repository graph; `graphify check-update <path>` is the cron-safe stale-graph check; `graphify diagnose multigraph` reports same-endpoint edge-collapse risk; and `graphify merge-driver <base> <current> <other>` is for a Git merge-driver invocation. Run `graphify --help` before supplying flags, and do not substitute these commands for the normal build/query workflow.
+
+---
+
 ## For /graphify add and --watch
 
 Neither is part of the default build. When the user runs `/graphify add <url>` to fetch a URL into the corpus, or passes `--watch` to auto-rebuild on file changes, see `references/add-watch.md`.

graphify/skill-opencode.md

@@ -684,6 +684,18 @@ Before traversal, expand the question against the graph's own vocabulary so a wo
 
 ---
 
+## For /graphify affected
+
+When the user asks for a change's blast radius or "what calls/depends on X?", use `graphify affected "X"` rather than a broad `query`. It reverse-traverses the graph from X and reports the callers and dependents that a change could impact. For relation/depth filters and the exact workflow, see `references/query.md`.
+
+---
+
+## Less-common maintenance commands
+
+Use these only when the request calls for them: `graphify tree` writes a collapsible hierarchy view; `graphify global add|remove|list|path` manages the cross-repository graph; `graphify check-update <path>` is the cron-safe stale-graph check; `graphify diagnose multigraph` reports same-endpoint edge-collapse risk; and `graphify merge-driver <base> <current> <other>` is for a Git merge-driver invocation. Run `graphify --help` before supplying flags, and do not substitute these commands for the normal build/query workflow.
+
+---
+
 ## For /graphify add and --watch
 
 Neither is part of the default build. When the user runs `/graphify add <url>` to fetch a URL into the corpus, or passes `--watch` to auto-rebuild on file changes, see `references/add-watch.md`.

graphify/skill-pi.md

@@ -692,6 +692,18 @@ Before traversal, expand the question against the graph's own vocabulary so a wo
 
 ---
 
+## For /graphify affected
+
+When the user asks for a change's blast radius or "what calls/depends on X?", use `graphify affected "X"` rather than a broad `query`. It reverse-traverses the graph from X and reports the callers and dependents that a change could impact. For relation/depth filters and the exact workflow, see `references/query.md`.
+
+---
+
+## Less-common maintenance commands
+
+Use these only when the request calls for them: `graphify tree` writes a collapsible hierarchy view; `graphify global add|remove|list|path` manages the cross-repository graph; `graphify check-update <path>` is the cron-safe stale-graph check; `graphify diagnose multigraph` reports same-endpoint edge-collapse risk; and `graphify merge-driver <base> <current> <other>` is for a Git merge-driver invocation. Run `graphify --help` before supplying flags, and do not substitute these commands for the normal build/query workflow.
+
+---
+
 ## For /graphify add and --watch
 
 Neither is part of the default build. When the user runs `/graphify add <url>` to fetch a URL into the corpus, or passes `--watch` to auto-rebuild on file changes, see `references/add-watch.md`.

graphify/skill-trae.md

@@ -690,6 +690,18 @@ Before traversal, expand the question against the graph's own vocabulary so a wo
 
 ---
 
+## For /graphify affected
+
+When the user asks for a change's blast radius or "what calls/depends on X?", use `graphify affected "X"` rather than a broad `query`. It reverse-traverses the graph from X and reports the callers and dependents that a change could impact. For relation/depth filters and the exact workflow, see `references/query.md`.
+
+---
+
+## Less-common maintenance commands
+
+Use these only when the request calls for them: `graphify tree` writes a collapsible hierarchy view; `graphify global add|remove|list|path` manages the cross-repository graph; `graphify check-update <path>` is the cron-safe stale-graph check; `graphify diagnose multigraph` reports same-endpoint edge-collapse risk; and `graphify merge-driver <base> <current> <other>` is for a Git merge-driver invocation. Run `graphify --help` before supplying flags, and do not substitute these commands for the normal build/query workflow.
+
+---
+
 ## For /graphify add and --watch
 
 Neither is part of the default build. When the user runs `/graphify add <url>` to fetch a URL into the corpus, or passes `--watch` to auto-rebuild on file changes, see `references/add-watch.md`.

graphify/skill-vscode.md

@@ -688,6 +688,18 @@ Before traversal, expand the question against the graph's own vocabulary so a wo
 
 ---
 
+## For /graphify affected
+
+When the user asks for a change's blast radius or "what calls/depends on X?", use `graphify affected "X"` rather than a broad `query`. It reverse-traverses the graph from X and reports the callers and dependents that a change could impact. For relation/depth filters and the exact workflow, see `references/query.md`.
+
+---
+
+## Less-common maintenance commands
+
+Use these only when the request calls for them: `graphify tree` writes a collapsible hierarchy view; `graphify global add|remove|list|path` manages the cross-repository graph; `graphify check-update <path>` is the cron-safe stale-graph check; `graphify diagnose multigraph` reports same-endpoint edge-collapse risk; and `graphify merge-driver <base> <current> <other>` is for a Git merge-driver invocation. Run `graphify --help` before supplying flags, and do not substitute these commands for the normal build/query workflow.
+
+---
+
 ## For /graphify add and --watch
 
 Neither is part of the default build. When the user runs `/graphify add <url>` to fetch a URL into the corpus, or passes `--watch` to auto-rebuild on file changes, see `references/add-watch.md`.

graphify/skill-windows.md

@@ -716,6 +716,18 @@ Before traversal, expand the question against the graph's own vocabulary so a wo
 
 ---
 
+## For /graphify affected
+
+When the user asks for a change's blast radius or "what calls/depends on X?", use `graphify affected "X"` rather than a broad `query`. It reverse-traverses the graph from X and reports the callers and dependents that a change could impact. For relation/depth filters and the exact workflow, see `references/query.md`.
+
+---
+
+## Less-common maintenance commands
+
+Use these only when the request calls for them: `graphify tree` writes a collapsible hierarchy view; `graphify global add|remove|list|path` manages the cross-repository graph; `graphify check-update <path>` is the cron-safe stale-graph check; `graphify diagnose multigraph` reports same-endpoint edge-collapse risk; and `graphify merge-driver <base> <current> <other>` is for a Git merge-driver invocation. Run `graphify --help` before supplying flags, and do not substitute these commands for the normal build/query workflow.
+
+---
+
 ## For /graphify add and --watch
 
 Neither is part of the default build. When the user runs `/graphify add <url>` to fetch a URL into the corpus, or passes `--watch` to auto-rebuild on file changes, see `references/add-watch.md`.

graphify/skill.md

@@ -692,6 +692,18 @@ Before traversal, expand the question against the graph's own vocabulary so a wo
 
 ---
 
+## For /graphify affected
+
+When the user asks for a change's blast radius or "what calls/depends on X?", use `graphify affected "X"` rather than a broad `query`. It reverse-traverses the graph from X and reports the callers and dependents that a change could impact. For relation/depth filters and the exact workflow, see `references/query.md`.
+
+---
+
+## Less-common maintenance commands
+
+Use these only when the request calls for them: `graphify tree` writes a collapsible hierarchy view; `graphify global add|remove|list|path` manages the cross-repository graph; `graphify check-update <path>` is the cron-safe stale-graph check; `graphify diagnose multigraph` reports same-endpoint edge-collapse risk; and `graphify merge-driver <base> <current> <other>` is for a Git merge-driver invocation. Run `graphify --help` before supplying flags, and do not substitute these commands for the normal build/query workflow.
+
+---
+
 ## For /graphify add and --watch
 
 Neither is part of the default build. When the user runs `/graphify add <url>` to fetch a URL into the corpus, or passes `--watch` to auto-rebuild on file changes, see `references/add-watch.md`.

graphify/skills/agents/references/query.md

@@ -20,6 +20,22 @@ if not Path('graphify-out/graph.json').exists():
 ```
 If it fails, stop and tell the user to run `/graphify <path>` first.
 
+## For /graphify affected
+
+Use `affected` for a deterministic reverse blast-radius answer: "what calls X?", "what depends on X?", or "what could a change to X impact?". Do not replace it with a broad natural-language `query` when the user is asking that question.
+
+```bash
+graphify affected "NODE_OR_LABEL"
+```
+
+The default depth is two reverse hops. Narrow the result when the user names a relationship, or widen it deliberately:
+
+```bash
+graphify affected "NODE_OR_LABEL" --relation calls --depth 3
+```
+
+Use `--graph PATH` when the graph is not at `graphify-out/graph.json`. Explain that the seed itself is the changed item; the printed nodes are the callers/dependents reached by the reverse traversal. If no nodes are found, report that the graph has no matching seed rather than inferring a negative result about the source repository.
+
 ### Step 0 — Constrained query expansion (REQUIRED before traversal)
 
 graphify's `query` CLI matches nodes via case-folded substring + IDF — there is **no stemming, no synonyms, no cross-language match** inside the binary, and the inline fallback below matches the same way. If the user's question uses different language or different domain vocabulary than the graph's labels (user says "обработчик" / graph says "handler"; user says "authentication" / graph says "Guardian"), the literal matcher returns 0 hits and the answer collapses to noise.