Skip to main content
You need to change something many parts of the code depend on: a core function, a data shape, a module boundary. The risk is the code you don’t know about. Graphify shows what a change reaches before you make it, and reviews the pull request against the same graph after. This walkthrough uses the open-source Graphify-Labs/graphify repository, with build_from_json as the function to change.

​
Walk through it

1

Map what the change reaches

With the repository Indexed (Index your first repository) and your agent connected (Claude Code, Cursor, Codex or VS Code), ask:
See Check the impact of a change.
2

Follow the callers

Ask what calls build_from_json, and trace how extract reaches it. See Follow calls and trace a path.
3

Look for code you can remove

Expand the repository row on Repositories to see Unreferenced code (heuristic). Code reached through reflection, a string lookup, or another repository can still appear, so check before you delete it.
4

Split the change and review it

Open the refactor as small pull requests. Each gets a review. Where verification ran, each supported changed function is proved equivalent, shows a behavior change with the input that triggers it, or has no verdict. See Review a pull request and Read a review and a verdict.
Impact results list direct connections. Code called dynamically, or tested in a way the graph does not link, may not appear. Run your tests.

​
Do it locally instead

After the refactor, rebuild with graphify update . --force. See Keep the graph current.

​
Next steps

Try it in Graphify

We build and host the graph for you. Start with a 14-day Pro trial, then keep up to 3 repositories on Free. No card required.