Map your backlog
Capture open issues, PRs, and their references. Explore linked work or ask your agent to group it by root cause.
Capture a backlogFind related work
before you start
Map related issues and pull requests. Prioritize your backlog, then open the exact view in your browser.
80 open items captured within an explicit budget
$ issue-graph open vercel-labs/portless --budget 80 --format json --no-open
vercel-labs/portless
Open items captured: 80References not crawled: 40
Saved locally. Collection stopped at the 80-item budget.
Next: ask your agent to group related work
issue-graph cluster vercel-labs/portless
$ issue-graph query github:vercel-labs/portless --state open --kind Issue --heat-top 25 --view rank --json --no-open
Captured: 80Matched: 10
Open issues · Heat ≥ 8.3
vercel-labs/portless#313OPENCloudflare tunnel support
Heat 33.2
vercel-labs/portless#326OPENAdd --no-worktree support when running apps with explicit names
Heat 26.6
First two results. Heat measures discussion, not severity.
$ issue-graph query github:vercel-labs/portless --state open --kind Issue --heat-top 25 --view rank --json --open
{
"opened": true
}
From backlog to your next task
Capture once, filter from the CLI, and open the same result in the dashboard. Structured output keeps your agent and your browser on the same work.
Choose what to inspect next
Filter by kind, state, cluster, or Heat. Rank open work with weights you control. Heat measures discussion, not severity.
Filter and rankOpen the exact view
Keep the CLI and dashboard on the same filters and weights. Explore in the browser or replay a saved query.
Use the dashboardUse issue-graph with your coding agent
Install the skill to let your agent inspect related work, propose clusters, and return a filtered dashboard link before making changes.
Read the agent workflowCollect
The CLI reads GitHub references and review states, and reports missing data.
Inspect
Your agent filters saved captures, ranks open work, and returns the exact dashboard view.
Decide
Review the suggested actions and check the code before closing issues or merging PRs.
Get started
Requires Node.js 20+
Sign in with GitHub CLI, then run issue-graph against a repository you can access.
Read the installation guide