gh-prs-monitor

Your GitHub pull requests, inside Claude Code.
See what needs you, know when it changes, and act on it from the list, or hand the work to a skill.

What it does · Get started · Features · Commands · Documentation · Issues

CI failed, a review came in, a teammate asked for your review: gh-prs-monitor tells you in the session you are already
in. /prs opens your pull requests with what needs you on top and a button for the next step: merge, re-run CI or ask
for a review in one press, or hand the fix to a skill. Nothing is written to GitHub without your yes. Try it on example
data with /prs demo.

What it does

• See what needs you. Your pull requests and the ones waiting on your review, what needs you on top.
• Know when it changes. An alert when CI fails, a review comes in or a pull request can merge, and a count in the
  status line.
• Act in one press. Merge, update a branch, re-run CI or ask for a review, each confirmed before it writes.
• Hand off the work. Skills resolve review comments, fix CI, resolve conflicts, review and open pull requests; the
  first three can work in a worktree of their own, so your checkout stays as it is.
• Look beyond this folder. Show another repository in the pane, and get alerts from the others if you like.
• Link your tickets. Paste one ticket link, and each pull request that names a ticket links it in Linear, Jira or
  whichever tracker you use: no token, no integration.
• Light on tokens. The pane, the checks and the alerts make no model requests; only a skill you start does.

A day with it follows a working day with the plugin, from the first session to the next
branch.

Get started

In Claude Code:

/plugin marketplace add maturada/gh-prs-monitor
/plugin install gh-prs-monitor@gh-prs-monitor

Choose Install for you (user scope) and run /reload-plugins. /prs demo shows example pull requests and sends
nothing to GitHub; /prs, in any folder whose git remote is on GitHub, shows your own. Esc closes the pane, and
/config sets when it checks and which alerts show. The pictures on this page show /prs demo or other made-up data.

You need the GitHub CLI signed in (gh auth login); Requirements has the
rest. gh-prs-monitor is a Claude Code plugin, installed with /plugin, not a gh extension.

Features

What needs you, on top

Your pull requests are sorted by what they need: failing and conflicting first, then what waits on you, then what is
ready to merge. The ones waiting on your review have a list of their own, and what someone else merged or closed lately
is noted under them. Failing checks, conflicts and unresolved comments link to where you deal with them on GitHub, and a
note under a row says what changed lately. Compact puts each on one line. The pane

Alerts while you work

Alerts come while you work, with no pane to keep open: when one of yours can merge, gets a review or a comment, fails CI
or runs into conflicts; when you are asked to review, or a pull request you reviewed without approving gets new commits;
when someone mentions you, or someone else merges or closes one of yours or one you review.

• They don't cut in. Alerts that come while Claude works wait for the turn to end, five minutes at most, and your
  sessions share which ones they showed, so a change alerts once.
• Coming back. It checks in the background, every three minutes by default: a new session sums up what changed
  since you last looked, and the status line keeps the count.
• Your way. /config picks the kinds; a sound and system notifications (in the terminal) are there too, off by
  default.

Alerts and the status line

One press for the routine

Each row offers the button its state calls for: Merge (stacked pull requests too), Auto-Merge,
Update Branch, Re-Run CI for the failed jobs, Ready For Review, Request Review with the people GitHub
suggests, and Re-Request Review. Each press looks at the pull request on GitHub first, offers only what your
repository allows, and asks before it writes; a merge goes through only while the pull request's head is still the
commit you saw. Acting on GitHub

Skills that do the work

• Resolve Comments sorts each unresolved comment as needs fix, debatable or already fixed, and fixes the ones you
  approve. More
• Fix CI reads the failing logs, tells a flaky failure from a real one, and fixes the ones you pick.
  More
• Resolve Conflicts merges the base in apart from your checkout, reads both sides and their commit messages, and
  proposes a resolution for each conflict, for you to approve. More
• Review leaves out what other reviewers and bots already raised, checks each finding before it shows it, and
  posts only the comments you approve. On a pull request you reviewed before, it can cover only what changed since and
  tell you what came of your comments. More
• Create PR runs the checks you pick, drafts the title and body in your repository's own format, and remembers your
  choices for next time. More

Resolve Comments, Fix CI and Resolve Conflicts ask where to work: in a worktree of their own, so your checkout and your
uncommitted changes stay as they are; in this checkout; or in a new session. A worktree comes ready, its dependencies
installed from the project's lockfile (JavaScript, Flutter and Dart, iOS, Python, Ruby, PHP, .NET) and your .env and
other ignored files copied as .worktreeinclude names them, and it goes once its pull request is done and nothing in it
would be lost. Review and Create PR run here or in a new session. Where the skills work

Your other repositories

Check on another repository without leaving this one. Press Repositories in the pane's header, beside Refresh, or
type /prs acme/web, /prs ~/code/web or a pull request's address; its buttons work there too, and Back returns to
this folder's list. Turn on Alerts from other repositories in /config for alerts about reviews and CI in the
others, and a +3 elsewhere count in the header. Other repositories

Your tickets, one click away

Paste a link to any ticket with /prs tickets, once per repository, and each pull request whose branch or title names
its key shows it on its row, WEB-5785 ⧉, a click away in Linear, Jira or whichever tracker you use. There is no token
and no integration: the plugin reads that one link on your machine and never contacts your tracker itself. Create PR
puts the ticket where your repository's pull requests do, and with your tracker's tool connected to Claude Code, Review
weighs the change against what the ticket asks, for you alone. Ticket links

Terminal, desktop app and VS Code

The pane opens beside the conversation in the terminal, in the Claude desktop app, and in the Claude Code extension for
VS Code and editors built on it, with the count in the status line, or in a band above the prompt in the desktop app.
From your phone or claude.ai over Remote Control, /prs prints the list in the conversation.
Where each part shows

Light on tokens

The pane, the checks, the alerts and the status line make no model requests; a skill does once you start it, and the
skills stay out of the model's context until one runs. The plugin's two tools add their descriptions, a few hundred
tokens. Each check is one main GitHub request, shared by your sessions in a repository: checking every 3 minutes uses 2%
of the 5,000 points an hour GitHub gives you, for each repository. Cost

Commands

Resolve Comments, Fix CI and Resolve Conflicts take a pull request's number or URL, or the current branch's without
one. Review needs a number or URL, and Create PR uses the branch checked out. Each takes instructions after --, as in
/gh-prs-monitor:review 142 since -- focus on the migration. The pane's buttons start the same skills, first asking
where to run.

Requirements

• Claude Code 2.1.292 or later; in VS Code and editors built on it, the Claude Code extension 2.1.299 or later.
• The GitHub CLI 2.53 or later, signed in with gh auth login. The plugin works through
  your account and has no token of its own.
• git 2.31 or later.
• A folder whose git remote is on GitHub: github.com, or GitHub Enterprise Server 3.16 or later.

The versions it is tested with, and what each setup needs:
Versions and setups.

Updates and removal

• Updates: in /plugin, under Marketplaces, select gh-prs-monitor and choose Enable auto-update, or
  Update now on the Installed tab. A new version loads in the next session, or after /reload-plugins.
  What each version changed: CHANGELOG.
• From a shell: claude plugin marketplace add maturada/gh-prs-monitor, then
  claude plugin install gh-prs-monitor@gh-prs-monitor; claude plugin update gh-prs-monitor@gh-prs-monitor
  updates it.
• To remove it: uninstall it in /plugin, or run claude plugin uninstall gh-prs-monitor@gh-prs-monitor.

What it runs and what it sends

The plugin makes no network request of its own. It works through your own gh and git, and the dependency installs
it runs for a skill fetch from the project's package registries, as running them yourself would. It writes nothing to
GitHub without your yes and keeps what it remembers on your machine. It has no server, no token of its own and no
telemetry, and reads no credential to sign in with.

It keeps, in Claude Code's plugin store on your machine: the last list and what you have seen of it for the 20
repositories you looked at last, the alerts shown, the answers your sessions share and which session is asking GitHub or
cleaning up a clone right now, the view you chose, your Create PR choices and ticket links, what cleanups left, and the
folders of the 50 clones your sessions loaded a list in last, with each one's repository. For the session alone, Claude
Code's plugin state holds a repository you show and what Alerts from other repositories read.

Every command, file and setting it touches, in full: What it runs and what it sends. More in
Privacy and
Security.

Documentation

• A day with it: a working day with the plugin
• The pane: the two lists, every status, the compact view, and where each part shows
• Alerts and the status line: what is alerted, and when
• Acting on GitHub: the buttons, and the dialog they ask in
• Resolve Comments, Fix CI,
  Resolve Conflicts, and where they work
• Review and Create PR
• Other repositories: showing another repository, and alerts from the others
• Ticket links: set up once per repository
• Settings and cost
• What it runs and what it sends
• When something is wrong
• Development: for contributors

Contributing and license

Bugs and ideas are welcome in the issues; /prs report opens one
with your versions filled in. How changes are made:
CONTRIBUTING.md.

MIT licensed, see LICENSE. Maintained by David Matura.