> ## 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. # Review pull requests locally with graphify prs > Review pull requests locally with graphify prs: see the impact of each change, find overlapping PRs with --conflicts, and rank the queue with --triage. Graphify can combine a repository’s graph with open pull request information. This workflow needs the GitHub CLI (`gh`) authenticated for the repository. ## Inspect the queue ```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} graphify prs graphify prs 42 graphify prs --conflicts ``` Replace `42` with a real PR number. The queue shows available CI, review, and graph-impact information. The conflicts view finds overlap in graph communities; it is a review signal, not a guarantee of textual conflicts or runtime breakage. ## Prioritize reviews ```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} graphify prs --triage ``` CLI triage uses an available configured model backend. Override it with `GRAPHIFY_TRIAGE_BACKEND` and optionally `GRAPHIFY_TRIAGE_MODEL` when needed. ## Target the correct repository ```bash theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} graphify prs --repo owner/repository --base main graphify prs --worktrees ``` Replace `owner/repository` and `main` with the repository and base branch you use. Keep the local graph current and aligned with that codebase before interpreting impact. ## MCP equivalent `list_prs`, `get_pr_impact`, and `triage_prs` expose PR context to an assistant. MCP `triage_prs` returns actionable PR data for the assistant to reason over; it is distinct from the CLI’s backend-assisted ranking. These commands inspect PRs. Merging and changing code remain separate actions in your normal workflow. ## Run it on a real repository These examples come from a code-only graph of the open-source [httpx](https://github.com/encode/httpx) repository, built with Graphify Local 0.9.97. Your counts will differ. The repository had 49 open pull requests, and `gh` was signed in. ```text theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} $ graphify prs graphify prs · base: master · 49 PRs # CI STATUS UPDATED IMPACT TITLE #3796 ✗ CI-FAIL 15d – Version 1.0 #3769 ✓ STALE 29d – Ensure mounted transports are closed even if main t… #3697 ✓ READY today – bugfix for zstd decompressobj reuse ... 10 ready · 2 CI failing · 37 stale · 1 wrong base ``` The IMPACT column showed `–` for most rows on the first run. It filled in on later runs, after `graphify prs 3769` and `--conflicts`. Open one pull request for its full impact: ```text theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} $ graphify prs 3769 PR #3769 · STALE Ensure mounted transports are closed even if main transport raises branch: fix/ensure-transport-cleanup-on-close -> master CI: ✓ SUCCESS review: REVIEW_REQUIRED Graph impact: 131 nodes / 14 communities files changed: 1 httpx/_client.py ``` `--conflicts` groups pull requests that touch the same community: ```text theme={"theme":{"light":"github-light-default","dark":"github-dark-default"}} Community 101 — .merge(), .copy_merge_params(), .__init__(), .update() (2 PRs overlap) #3710 STALE Keep original host on IDNA decode errors #3618 STALE Fix URL params to merge with existing query parameters… ``` A shared community means two changes touch related code, so review them together. It doesn't mean they will conflict in git. ## Troubleshooting **`Triage failed: No module named 'openai'`.** `--triage` needs a model backend. Install the extra for your backend, such as `graphifyy[openai]` or `graphifyy[gemini]`, and set its API key. When triage fails, the normal queue still prints. **`Error: gh CLI not found or not authenticated. Run: gh auth login`.** Install the GitHub CLI and run `gh auth login` for the repository's host. We saw this error from `--worktrees` even though `gh pr list` worked in the same shell. If that happens to you, run the command from inside the git repository and confirm `gh auth status`. **The impact numbers look wrong.** Impact comes from your local graph. Run `graphify update .` on the base branch first. ## Flags These come from the argument parser in `graphify/prs.py`: | Flag | What it does | | - | - | | `` | Shows one pull request with its graph impact and changed files. | | `--conflicts` | Groups open pull requests by the communities they share. | | `--triage` | Ranks the queue with a configured model backend. | | `--worktrees` | Maps pull requests to local git worktrees. | | `--wrong-base` | Shows pull requests that target a branch other than the base. | | `--base B`, `-b B` | Sets the base branch. The default is the repository's default branch. | | `--repo OWNER/NAME`, `-R` | Targets a repository other than the current one. | | `--graph PATH` | Reads a different `graph.json`. | The status column uses READY, STALE and CI-FAIL, and the summary line counts pull requests on the wrong base. In the httpx run that was "1 wrong base". ## FAQ **Does `graphify prs` change anything on GitHub?** No. It reads pull requests through `gh` and prints them. ## 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)** > > Get graph-aware review comments automatically. > **[Read a review and a verdict](https://docs.graphify.com/platform/read-a-result.md)** > > What each finding means. [PreviousShare context with your team](https://docs.graphify.com/cookbooks/shared-team-graph.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.