---
title: "@henryqw/pi-pr"
seo:
  description: "Show the current branch pull request status in the Pi footer."
---

<div class="not-prose my-6 flex flex-wrap items-center gap-3"><span class="text-sm text-muted-foreground">v0.3.6</span><a href="https://www.npmjs.com/package/@henryqw/pi-pr" aria-label="View @henryqw/pi-pr on npm"><img alt="Monthly npm downloads" height="20" src="https://img.shields.io/npm/dm/%40henryqw%2Fpi-pr?cacheSeconds=7200&amp;color=1d4ed8&amp;label=downloads&amp;labelColor=101828&amp;style=flat-square" width="144"></a></div>

Show the current branch pull request's lifecycle, CI, mergeability, and review state in the Pi footer.

## Why

- **Created for**: Avoid repeated `gh` commands just to check pull-request status during work.
- **Advantage**: Branch lifecycle, CI, mergeability, and review state appear at a glance in the footer.

## Install

```bash
pi install npm:@henryqw/pi-pr
```

Requires authenticated GitHub CLI access (`gh auth login`) in a GitHub repository checkout.

## With

`@henryqw/pi-footer` improves this package by showing current-branch pull-request status in the footer.

## Use

| Surface | Type | Purpose |
| --- | --- | --- |
| Footer | ui | Show the current branch pull request. |
| `/pr` | command | Open current branch PR, or start PR workflow when absent. |

Each entry is one linked `PR #number` plus one plain-language state. Possible states are:

- `<count> unresolved`, `draft`, `open`, `approved`, and `CI running`
- `CI failed`, `changes requested`, `merge conflict`, `merged`, and `closed`

Colors support text. They do not carry meaning alone.

Known states have this priority:

1. `<count> unresolved` for known unresolved review threads
2. `merge conflict`
3. `changes requested`
4. `CI failed`
5. `CI running` for CI progress

The status loads at session start and polls every 30 seconds. It refreshes after an agent successfully runs `gh pr create`, `git push`, or `/pr`.

Unresolved review threads are checked every 30 seconds for 20 minutes after an open PR is first found. Each new push or remote PR update, including new comments, restarts that window.

The footer and warning notification show the unresolved count when first found or increased. The last known footer count remains after review checks stop. No pull request leaves the footer blank.

`/pr` finds an open PR for the current branch. When absent, it starts bundled `/skill:pi-pr-create` workflow.

The agent resolves the base and inspects and commits scoped changes. It runs relevant validation, pushes the branch, and creates or updates the PR with a live title and body.

This workflow handles dirty worktrees. It never silently commits unrelated changes.