issue-graph CLI
A GitHub CLI and skill that maps linked issues and PRs, surfacing competing fixes and unresolved follow-ups before you start.
- 184 ★ on the repository
- Last commit
- Apache-2.0
Minimal access
Why this level
- Reads GitHub data through your login and saves local snapshots.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/issue-graphDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- Reads GitHub data through your login and saves local snapshots.
This is third-party code. Review the repository files before installing.
What it does
`issue-graph` follows links between GitHub issues and pull requests and builds a graph: existing fixes, regressions, open follow-ups. `graph` inspects one item, `rank` orders open issues by label, `status` counts open PRs per author, and `reconcile` with `plan` pick the next backlog action. The agent skill is installed separately and tells the agent to read the guidance bundled with the CLI via `issue-graph skills get core` first. All reads go through your `gh` login, and results can be exported to JSON or a local HTML dashboard and saved under `~/.issue-graph/`.
Who it is for. Maintainers and developers triaging a repository backlog with an agent who want to avoid duplicating existing work.
Good fit when
- Before fixing a bug you want to know whether another PR already covers it.
- A review starts with which open PRs compete with or supersede each other.
- The team needs a count of open PRs per author.
- An agent picks the next backlog task from data rather than a guess.
Not a fit when
- The repository is not on GitHub: Linear and Jira are not read live.
- You need to modify issues or PRs; the tool is read-only.
- You would close a task from the graph alone without checking the code.
Example request
Build a graph for issue 1113 at depth 1, show linked PRs and list open follow-ups separately.Limitations
Requires Node.js 20 or newer and a `gh auth login` session. Coverage depends on traversal depth, node caps and permissions, so check the report for missing references. Snapshots, exports and clustering prompts can contain private repository metadata, and anyone holding an HTML export can read it. The README follows main, which can run ahead of the published npm package.
How to disable. Remove the skill from the agent skills directory and run `npm uninstall --global issue-graph`. Saved snapshots live in `~/.issue-graph/` and are deleted by hand.
FAQ
Does the tool change issues or PRs?
No. The skill is described as read-only context: it reads GitHub and writes only local snapshots and exports.
How do I try it without installing?
Run `npx issue-graph@latest --help`. Live queries need a `gh auth login` session.
What does the `status` command do?
It counts open PRs per author, for example `issue-graph status vercel-labs/portless --author ctate`. Unknown values show as `?` or `null`.
Where are snapshots stored?
In `~/.issue-graph/` by default. The `ISSUE_GRAPH_HOME` variable changes the path and `--no-save` skips history.
What if the `skills` command is missing?
The skill tells the agent to stop and report the CLI and skill mismatch rather than improvise from memory. Update the package with `npm install --global issue-graph@latest`.
Discussion
No questions or reviews yet.
Related
CLI toolsA Go tool for GitHub issues: Markdown files on disk that an agent edits in bulk and the push command sends back.
ghfs keeps GitHub issues and pull requests as Markdown files so an agent can read them offline and edit them in bulk
The /graphify skill builds a knowledge graph of a project's code, docs and PDFs so the agent queries the graph instead of grepping
The GitHub CLI extension gh stack and an agent skill: a chain of dependent branches and PRs with rebase, submit and merge of the whole stack
A skill with four gh scripts that gives an agent pull request state, review threads and CI failures in one call and short output.
Code graph and project memory in one Rust program: the agent gets excerpts with file and line citations
README in short
The tool runs on live GitHub data, so results change between runs. The README demonstrates it on issue 1113 from the agent-browser repository.