Shipping a new subcommand today: graphify prs.
The problem it solves: no existing PR dashboard knows your codebase structure. You can see CI state and review decisions — but you cannot see that two open PRs both touch the auth community and are going to conflict at merge time. graphify prs does.
What it does
graphify prs # dashboard: CI state, review decision, worktree mapping
graphify prs 42 # deep dive on one PR — blast radius, communities touched
graphify prs --conflicts # PRs sharing graph communities → merge-order risk
graphify prs --triage # AI ranks your review queue by graph impact
graphify prs --worktrees # worktree → branch → PR in one view
graphify prs --repo owner/repo # works on any GitHub repoGraph impact
The --conflicts view crosses your open PRs against the knowledge graph. If two PRs touch the same community of nodes, they get flagged — with representative node labels so you know what that community actually is (ValidateToken, SessionStore, AuthMiddleware) rather than just "Community 3".
The dashboard shows a blast radius column per PR: 14 nodes / 3 communities. High number = review this carefully before merging.
Triage
--triage sends your PR queue to whatever LLM backend you have configured and gets a ranked list with one action per PR. Auto-detects from your env: claude → kimi → openai → gemini → claude-cli → ollama. Override with GRAPHIFY_TRIAGE_BACKEND.
MCP
Three new tools on the MCP server: list_prs, get_pr_impact, triage_prs. Your agent can now query PR state the same way it queries the graph.
Install
pip install --upgrade graphifyyNo new required dependencies. Requires gh CLI authenticated for PR data.