Review pull requests locally with graphify prs

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

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

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

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 repository, built with Graphify Local 0.9.97. Your counts will differ. The repository had 49 open pull requests, and gh was signed in.

$ 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:

$ 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:

  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
`<number>`	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

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

Get graph-aware review comments automatically.

Read a review and a verdict

What each finding means.

Get started

Features

Configuration

Support

Review pull requests locally with graphify prs

Inspect the queue

Prioritize reviews

Target the correct repository

MCP equivalent

Run it on a real repository

Troubleshooting

Flags

FAQ

Next steps

Try it in Graphify

Pull request reviews

Read a review and a verdict

​Inspect the queue

​Prioritize reviews

​Target the correct repository

​MCP equivalent

​Run it on a real repository

​Troubleshooting

​Flags

​FAQ

​Next steps

Try it in Graphify

Pull request reviews

Read a review and a verdict

Inspect the queue

Prioritize reviews

Target the correct repository

MCP equivalent

Run it on a real repository

Troubleshooting

Flags

FAQ

Next steps