Skip to main content
Before you change a function or a file, ask your agent what the change reaches. Graphify reads the graph of your indexed repository and returns the connected code, hotspot files ranked by linked-test coverage, and the tests linked to them. Use this while you plan a change. After you open a pull request, pull request reviews check the change itself.

Before you start

  • An account at app.graphify.com. The Free plan (up to 3 repositories) needs no card. Pro and Teams start with a 14-day trial, card required.
  • A repository with the status Indexed. See Repositories and builds.
  • Your agent connected to the hosted MCP server at https://api.graphify.com/mcp. See Code with an agent.

Ask about the change

Name the symbol or the file you plan to change. Your agent uses these hosted tools: For a deeper look, ask for the callers of the symbol. See Follow calls and trace a path.

Read the result

Treat the result as a starting list, not a full answer:
  • graphify_impact returns direct connections only: the callers and callees of the symbol. Code that is called dynamically, or connected through several steps, may not appear.
  • include_risk ranks hotspot files by linked-test coverage. That ranking is a signal from the graph, not a verdict that the change is safe.
  • A file with no linked tests in the result may still be tested in a way the graph does not link.
  • Each edge carries a confidence tag (EXTRACTED, INFERRED, or AMBIGUOUS). Edges and provenance explains each tag.
Read the code your agent lists before you change it.

If something fails

Next steps

Try it in Graphify

We build and host the graph for you, and review your pull requests with it. The Free plan (up to 3 repositories) needs no card. Pro and Teams start with a 14-day trial, card required.

Pull request reviews

What Graphify checks once you open the pull request.

Read a review and a verdict

How to read what a review returns.