npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@henryqw/pi-pr

v0.3.2

Published

Show the current branch pull request status in the Pi footer.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

henrywanghenrywang

Keywords

pi-packagepigithubpull-requestfooter

Readme

@henryqw/pi-pr

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

Why

  • Created for: Avoiding 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.

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: <count> unresolved, draft, open, approved, CI running, CI failed, changes requested, merge conflict, merged, or closed. Known unresolved review threads take priority, followed by merge conflict, changes requested, CI failure, then CI progress. Colors support text; they do not carry meaning alone.

The status loads at session start, polls every 30 seconds, and 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. Footer and warning notification show the unresolved count when first found or increased. Last known footer count remains after review checks stop. No pull request leaves the footer blank.

/pr finds an open PR for current branch. When absent, it starts bundled /skill:pi-pr-create workflow. Agent resolves base, inspects and commits scoped changes, runs relevant validation, pushes branch, and creates or updates PR with live title and body. This workflow handles dirty worktrees; it never silently commits unrelated changes.

Remove

pi remove npm:@henryqw/pi-pr

Development

npm test --workspace @henryqw/pi-pr
npm run typecheck --workspace @henryqw/pi-pr
npm run pack:check --workspace @henryqw/pi-pr