> ## Documentation Index
> Fetch the complete documentation index at: https://docs.graphify.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> The PyPI package is graphifyy, with two y's. The command is graphify.
> /graphify . is typed in an assistant chat, not in a shell.
> Use only commands, flags, and endpoints shown on these pages. Do not invent one.
> Choose the surface before you open a page. Local is the graphifyy package on the machine: the skill, the CLI, and the ten-tool MCP. Its pages are the Guides and Reference tabs, /mcp/ (except /mcp/docs-search, which is for both), and the Local skill group in Integrations. Cloud (Graphify Cloud) is the hosted workspace and https://api.graphify.com/mcp (Streamable HTTP, OAuth, no API key). Its pages are the Graphify tab (/platform/) and the Cloud MCP group in Integrations. Concepts, troubleshooting, pricing, and /platform/local-to-cloud apply to both. Each page's source frontmatter records this as surface: local, cloud, or both. Buildkite is the CI integration.
> In llms.txt, tell the surface from the page path. Cloud: /platform/ and /integrations/ cloud, vscode, jetbrains, chatgpt, openclaw, vercel, other-agents, buildkite. Local: /guides/, /reference/, /mcp/overview, /mcp/shared-http, /installation, /quickstart, and /integrations/ claude-code, cursor, codex, gemini-cli, copilot, other-assistants. Everything else applies to both.
> graphifyy release notes are published at https://github.com/Graphify-Labs/graphify/releases and https://graphify.com/changelog. The current package version is on PyPI (https://pypi.org/project/graphifyy/).
> The official site is https://graphify.com. These docs are https://docs.graphify.com.
> The local MCP server is the ten tools in the MCP tool reference and reads a graph on the machine. The hosted server is https://api.graphify.com/mcp (Streamable HTTP, OAuth, no API key). The VS Code, JetBrains, OpenClaw, Vercel, and Other Cloud agents pages, and the page ChatGPT, Codex, and Dots, use the hosted server, not the ten-tool list. Other local assistants is the local skill for clients without their own page. The page titled Graphify with Codex is the local skill.
> Read https://docs.graphify.com/llms.txt, then open one page's .md link. Use https://docs.graphify.com/llms-full.txt only when one page is not enough.

# Check the impact of a change before you make it

> Ask your agent what a change to a symbol or file reaches in your indexed repository, which files carry the most risk, and which tests cover them.

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, the files where a change fans out most widely, and the tests linked to them.

Use this while you plan a change. After you open a pull request, [pull request reviews](https://docs.graphify.com/platform/reviews.md) check the change itself.

## Before you start

* An account at [app.graphify.com](https://app.graphify.com). The Free plan covers 3 indexed repositories, and you don't need a card.
* A repository with the status **Indexed**. See [Repositories and builds](https://docs.graphify.com/platform/repositories.md).
* Your agent connected to the hosted MCP server at `https://api.graphify.com/mcp`. See [Code with an agent](https://docs.graphify.com/guides/cloud-coding-agents.md).

## Ask about the change

```text Agent prompt theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}}
Use Graphify on Graphify-Labs/graphify: I want to change build_from_json.
What does that change reach, which files are riskiest, and which tests cover them?
```

Name the symbol or the file you plan to change. Your agent uses these hosted tools:

| Tool | What it returns |
| - | - |
| `graphify_impact` | The code directly connected to a symbol. A first pass at what a change reaches. |
| `impact_and_risk` | Files ranked by how widely a change fans out, and whether tests cover them. |
| `graphify_tests_for` | Tests linked to a symbol or a file. |
| `graphify_file_neighbors` | A file's imports, and the files that import it. |

For a deeper look, ask for the callers of the symbol. See [Follow calls and trace a path](https://docs.graphify.com/concepts/follow-calls.md).

## Read the result

Treat the result as a starting list, not a full answer:

* `graphify_impact` returns direct connections only. Code that is called dynamically, or connected through several steps, may not appear.
* 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](https://docs.graphify.com/concepts/provenance.md) explains each tag.

Read the code your agent lists before you change it.

## If something fails

| What you see | What to do |
| - | - |
| The wrong symbol is used | Give the full name or the file it lives in. |
| Very few results | Check that the latest build is **Indexed**, then ask for callers to go further. |
| No tests listed | Ask your agent to search the test folders, then run the tests you find. |

## Next steps

> **[Try it in Graphify Cloud](https://docs.graphify.com/platform/quickstart.md)**
>
> We build and host the graph for you. Free for up to 3 repositories, no card required.

> **[Pull request reviews](https://docs.graphify.com/platform/reviews.md)**
>
> What Graphify checks once you open the pull request.

> **[Read a review and a verdict](https://docs.graphify.com/platform/read-a-result.md)**
>
> How to read what a review returns.

[PreviousFollow calls and trace a path](https://docs.graphify.com/concepts/follow-calls.md)
[NextPull request reviews](https://docs.graphify.com/platform/reviews.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.