Skip to content

pr-status

Know where you standv1.0.0

Your pull request's CI checks, live above the prompt.

claude: pr-status
What you are seeing A band above the prompt shows a pull request's checks running, then one failing. After Claude fixes it, all five pass and a toast says so.

Install

o-mods
  1. Add the o-mods collection (once):

    claude plugin marketplace add omeerdvrn/o-mods

  2. Install this mod:

    claude plugin install pr-status@o-mods

Then run /reload-plugins in any open Claude Code session.

First time? Set up o-mods

Author
omeerdvrn
Version
1.0.0
License
MIT
Tags
pr, ci, github, gitlab, gitea, bitbucket, azure-devops
Source on GitHub
Source on GitHub

Shows the CI status of the current branch's pull request in a band above the prompt. The band appears as soon as the branch has an open PR, counts its checks by state, and updates while they run:

PR #842  ✗ 1 failed  ⟳ 2 running  ○ 1 queued  ✓ 8 passed  feat(ENG-3331): parity follow-ups   [ Open ] [ Hide ]
  failing: CI / integration (pull_request)

A toast tells you when CI finishes, passed or failed.

Forges ​

The mod reads the branch's upstream remote (or origin) and detects the forge on its own:

ForgeHow it reads the PRCredentials
GitHub, GitHub Enterprisegh pr view, or the REST APIgh auth login, or GH_TOKEN/GITHUB_TOKEN
GitLab, self-hosted GitLabglab api, or the REST API: the MR's head pipeline jobsglab auth login, or GITLAB_TOKEN/GL_TOKEN
Gitea, Forgejo, Codebergtea pulls list, or the REST API: commit statuses (Gitea Actions report here)tea login add, or GITEA_TOKEN/FORGEJO_TOKEN/CODEBERG_TOKEN
Bitbucket CloudREST API: the PR's statusesBITBUCKET_TOKEN, or BITBUCKET_USERNAME + BITBUCKET_APP_PASSWORD; public repos need none
Azure DevOpsREST API: builds of the PR's merge ref and PR statusesAZURE_DEVOPS_EXT_PAT

Detection, in order:

  1. An SSH alias such as github.com-work resolves to its real host through ssh -G.
  2. Well-known hosts: github.com, gitlab.com, bitbucket.org, dev.azure.com, *.visualstudio.com, codeberg.org, and hosts named github.*, gitlab.*, gitea.* or forgejo.*.
  3. A host that tea, glab or gh is signed in to.
  4. A probe of the host's API: /api/v1/version (Gitea, Forgejo), /api/v4/version (GitLab), /api/v3/meta (GitHub Enterprise).

Each host's result is remembered on this machine.

Check states ​

GlyphStateIncludes
✓passedsuccess
✗failedfailure, error, timed out, action required
⟳runningin progress, pending
○queuedqueued, waiting, created, scheduled
⚠warningGitea warning, GitLab allowed failure, Azure partially succeeded
⊘cancelledcancelled, stopped, stale
–skippedskipped, neutral, manual

When a check is re-run, only its newest result is counted.

When it updates ​

  • Every 10 seconds while any check is running or queued.
  • Every 60 seconds once all checks have settled.
  • Every 30 seconds while the branch has no PR, so the band appears shortly after a PR is opened from anywhere.
  • Right away after Claude runs git push, git checkout/switch, gh pr create, glab mr create, tea pr create, az repos pr create, or a CI re-run, and again 5 seconds later. Also after Claude enters or leaves a worktree.

Command ​

/pr-status           # refresh, then list every check (failed ones with their links)
/pr-status 123       # pin PR 123 (or #123): the band follows that PR instead of the branch's
/pr-status branch    # follow the branch's open PR again
/pr-status open      # open the PR in the browser
/pr-status hide      # hide the band until the next PR
/pr-status show

Develop ​

claude plugin validate mods/pr-status
claude plugin test mods/pr-status

Edit this page on GitHub