pi-pr-status

A Pi extension that shows the current PR link, CI check status, and unresolved review comments in the footer status bar

Package details

← Back
extension

Install pi-pr-status from npm and Pi will load the resources declared by the package manifest.

npm repohome report
$ pi install npm:pi-pr-status
Package
pi-pr-status
Version
0.3.0
Published
Feb 16, 2026
Downloads
24/mo · 11/wk
Author
brunogarcia
License
MIT
Types
extension
Size
13.8 KB
Dependencies
0 dependencies · 1 peer
Pi manifest JSON
{
  "extensions": [
    "./extensions"
  ]
}

Security note

Pi packages can execute code and influence agent behavior. Review the source before installing third-party packages.

README

pi-pr-status

A Pi extension that shows your current PR's status right in the footer — so you always know which PR you're working on, whether CI is green, and if there are review comments to address.

What it shows

When your current git branch has an open pull request, the footer displays:

🟢 PR #42 · ✅ 5 checks passed · https://github.com/owner/repo/pull/42

CI failures?

🟢 PR #42 · ❌ 2/5 checks failed · https://github.com/owner/repo/pull/42

Checks still running?

🟢 PR #42 · ⏳ 3/5 checks pending · https://github.com/owner/repo/pull/42

Unresolved review comments?

🟢 PR #42 · ✅ 5 checks passed · 💬 3 unresolved · https://github.com/owner/repo/pull/42

PR state icons:

Icon State
🟢 Open
🟣 Merged
🔴 Closed

When there's no PR for the current branch, nothing is shown.

Requirements

  • Pi coding agent
  • GitHub CLI (gh) — authenticated with gh auth login

Install

pi install npm:pi-pr-status

Or try it without installing:

pi -e npm:pi-pr-status

You can also install from git:

pi install git:github.com/bruno-garcia/pi-pr-status

How it works

  1. Detects the current git branch
  2. Runs gh pr view to find the associated pull request
  3. Parses CI status check results (pass / fail / pending)
  4. Queries unresolved review threads via the GitHub GraphQL API
  5. Displays everything in the pi footer status bar

The extension polls every 30 seconds to pick up CI and review changes. Repo metadata is cached so only two API calls are made per poll (one for PR + checks, one GraphQL query for review threads). When no PR exists for the branch, no API calls are made after the initial check.

Development

npm install
npm test

License

MIT