Skip to content
Henry Pi Harness
Esc
navigateopen⌘Jpreview
On this page

@henryqw/pi-pr

v0.3.6Monthly npm downloads

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

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.

Was this page helpful?