> ## 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.
# Review pull requests with graph context
> Inspect changed areas, overlapping work, and review priorities.
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={null}
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={null}
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={null}
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.