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 to Cursor, the Graphify extension for VS Code, the Graphify plugin for ChatGPT and Codex, or the hosted MCP setup. 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.” Every other tool takes that repository_id, either the UUID or owner/name.

​
Review a pull request

Triggers: graphify_impact, impact_and_risk, graphify_tests_for. These tools read the graph. They don’t run tests.

​
Check the impact of a change

Triggers: graphify_impact, which takes the symbol name directly. It returns the callers and callees directly connected to it, grouped by file. That’s a first pass, not every transitive effect. If several symbols share the name, the results combine them: check the resolved symbol and the seeds.

​
Find where something is called

Triggers: graphify_callers, which takes the symbol name directly and returns each caller with its file, definition line and call_site line. If the name matches several symbols, it lists them under ambiguous. By default it returns only resolved call edges; ask for strict_calls=false to include inferred ones. An empty list means the index found no callers. 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 and shows the matching symbols in each, then query_graph, which returns the relevant definitions to explain from. Agents often add graphify_trace to follow a path. If it finds no direct call path, it returns where it stopped instead. In workspaces with trail capture turned on, these calls can save the question to workspace memory. For a lighter, read-only first look, ask for graph_stats and graphify_find_seeds.

​
Make it stick

  • Every result carries freshness: the indexed commit and its age. 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.