> ## 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 (Graphify Local) is the graphifyy package on the machine: the skill, the CLI, and the ten-tool MCP. Its pages are the Open Source tab (/open-source/) and the Graphify Local tab on each Integrations page. Graphify is the hosted workspace and https://api.graphify.com/mcp (Streamable HTTP, OAuth, no API key). Its pages are the Graphify tab (/platform/, /concepts/) and the Graphify (hosted) tab on each Integrations page. Prefer Graphify unless the user asks for a local or offline setup. Cookbooks (/cookbooks/) and /mcp/docs-search 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. Graphify: /platform/ and /concepts/. Local: /open-source/. Most /integrations/ pages cover both, with a Graphify (hosted) tab and a Graphify Local tab. 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 JetBrains, ChatGPT, Codex, and Dots, and Vercel pages use the hosted server, not the ten-tool list. On pages with tabs, the Graphify (hosted) tab uses the hosted server and the Graphify Local tab uses the local skill or the ten-tool server. > 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. # Find pull requests that collide before you merge > Find open pull requests that change the same part of your code graph, see the merge-order risk with graphify prs, and rank the review queue with a model. Two pull requests can both pass review and still collide when they change the same part of the code. Graphify compares open pull requests against the graph of your repository and shows which ones touch the same area, so you can review and merge them with that in mind. ## Before you start * An account at [app.graphify.com](https://app.graphify.com). New accounts start on a 14-day Pro trial, then move to Free (up to 3 indexed repositories). No card is required. * For the local commands, the open-source CLI. See [Installation](https://docs.graphify.com/open-source/installation.md). * A repository with the status **Indexed**, or a local graph at `graphify-out/graph.json`. * For the local commands, the [GitHub CLI](https://cli.github.com) signed in to the repository. `graphify prs` reads open pull requests through it. ## In Graphify On a connected repository, Graphify checks each pull request for cross-branch conflicts with the other open pull requests and gives a merge order. It does this along with the [review](https://docs.graphify.com/platform/reviews.md) of each pull request. Like the review, it is advisory and doesn't block a merge. ## With the local CLI From the repository root, list the open pull requests that share a graph community: ```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} graphify prs --conflicts ``` The output groups pull requests by community, with the number of pull requests that overlap in each. This is a merge-order *risk* signal. It does not give a merge order, and it does not promise a textual conflict or a runtime break. If no open pull requests overlap, the command says so. To have a model rank the review queue: ```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} graphify prs --triage ``` Triage uses the first model backend it finds configured. Set `GRAPHIFY_TRIAGE_BACKEND`, and optionally `GRAPHIFY_TRIAGE_MODEL`, to choose one. | Option | Meaning | | - | - | | `--conflicts` | Group open pull requests that share a graph community. | | `--triage` | Rank the review queue with a model. | | `--base ` | Only pull requests that target this branch. Defaults to the repository's default branch. | | `--repo ` | Read pull requests from another repository. | | `--graph ` | The graph file to use. | | `` | Show one pull request with its graph impact. | For example, on a clone of the open-source repository: ```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} git clone https://github.com/Graphify-Labs/graphify && cd graphify graphify extract . --code-only graphify prs --conflicts --repo Graphify-Labs/graphify ``` ## Read the result Pull requests in the same community change code that is closely connected in the graph. Review them together and agree an order. After each merge, rebase the others and run your tests. A pull request missing from the list can still conflict in ways the graph does not show, such as config or generated files. ## If something fails | What you see | What to do | | - | - | | "No graph impact data" | Build or point to a graph: run `graphify extract . --code-only`, or pass `--graph`. | | No pull requests listed | Check `--base`. Only pull requests that target that branch are compared. | | An error from `gh` | Sign in with `gh auth login` and check you can see the repository. | | Triage can't find a backend | Set `GRAPHIFY_TRIAGE_BACKEND` and the API key for that backend. | [Pull request context](https://docs.graphify.com/open-source/features/pr-impact.md) covers the rest of `graphify prs` and the MCP tools for pull requests. ## Next steps > **[Try it in Graphify](https://docs.graphify.com/platform/quickstart.md)** > > 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. > **[Pull request reviews](https://docs.graphify.com/platform/reviews.md)** > > What Graphify checks on each pull request. > **[Check the impact of a change](https://docs.graphify.com/concepts/check-impact.md)** > > See what a change reaches before you open it. [PreviousRead a review and a verdict](https://docs.graphify.com/platform/read-a-result.md) [NextFormal verification](https://docs.graphify.com/platform/verification.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.