Skip to main content
Paste these prompts into any agent connected to Graphify. Each one names the tool it should trigger, so you can check that the agent used the graph instead of searching files one by one. Not connected yet? Use Connect Graphify in Claude (Claude.ai and Desktop, Claude Code), Connect to Cursor, the Graphify extension for VS Code, the Graphify plugin for ChatGPT and Codex, or Graphify MCP. Hosted Graphify lists 63 grammars. Open-source Graphify supports 40 languages (33 tree-sitter, 7 built-in).
Start each session with “Use Graphify’s list_repositories tool and pick the repository for this project.” Most repository tools take that repository_id, either the UUID or owner/name. You can omit it when the connection URL sets ?repo= or the workspace has one repository.

Review a pull request

Triggers: graphify_impact with include_risk, and graphify_tests_for. These tools read the graph. They don’t run tests. include_risk ranks hotspot files by linked-test coverage. That ranking is a signal from the graph, not a verdict.

Check the impact of a change

Triggers: graphify_impact, which takes the symbol name as target. It returns the callers and callees directly connected to it. That’s a first pass, not every transitive effect. Set include_risk to also rank hotspot files by linked-test coverage.

Find where something is called

Triggers: graphify_callers, which takes the symbol name as symbol. If the name matches several definitions, it refuses and lists the candidate ids. Pass an id to pick one. By default it returns only resolved call edges (strict_calls is true). Set strict_calls to false to include inferred ones. An empty list means no call edge was indexed. It doesn’t prove the code is unused, because dynamic calls can be missed.

Find the tests for a symbol

Triggers: graphify_tests_for. It accepts a symbol or a file path and returns test files and test functions linked through imports and calls. Linked tests aren’t a guarantee of runtime coverage.

Onboard to a new codebase

Triggers: graphify_rank_files, which ranks files for the question, then query_graph, which returns the relevant definitions to explain from. For a lighter first look, ask for graph_stats, or query_graph with skeleton so you get outlines instead of full definition bodies.

Follow a call path

Triggers: graphify_trace, from src to tgt. If a name does not resolve, it can fall back to a semantic match. Check resolved.src and resolved.tgt. An empty path means no directed call path was found in the indexed graph.

Make it stick

  • The graph reflects the last indexed snapshot of the default branch. If your branch has new code, say so and expect gaps. See Keep answers fresh.
  • remember saves a note for later sessions. Your agent should ask before calling it.
  • To make your agent use Graphify without being told, add a project rule. See Make agents use the graph.

Agents use Graphify

The full question-to-tool map.

Cloud coding agents

Step-by-step hosted MCP walkthrough.