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

pi-shit

v0.4.2

Published

Personal Pi package bundling extensions, skills, and Rose Pine themes

Vulnerabilities

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

Links

Git

Maintainers

ferologicsferologics

Keywords

pi-packagepi-extensionpi-skillpi-theme

Readme

pi-shit

Combined Pi package for personal extensions + skills.

Structure

  • extensions/ → Pi extensions (for example deep-review, pi-system-theme, plan-mode)
  • skills/ → Pi skills (including pr-context-packer)
  • themes/ → Pi themes (rose-pine, rose-pine-dawn)

Install in Pi

pi install npm:pi-shit

Or from git/local:

pi install git:github.com/ferologics/pi-shit
pi install /path/to/pi-shit

Sync workflow

Primary flow (monorepo-first): edit in this repo, then publish mirrors.

just publish

just publish fans out to:

  • skills/ → pi-skills
  • extensions/ → pi-extensions
  • extensions/deep-review/ → pi-deep-review
  • extensions/pi-notify/ → pi-notify
  • extensions/pi-system-theme/ → pi-system-theme

Or publish individually:

just publish-skills
just publish-extensions
just publish-pi-deep-review
just publish-pi-notify
just publish-pi-system-theme

Repair-only flow (use only for emergency downstream hotfixes; normal work should stay in pi-shit):

just pull-skills
just pull-extensions
just pull-pi-deep-review
just pull-pi-notify
just pull-pi-system-theme

Theme sync still pulls from zenobi-us/pi-rose-pine:

just update-themes

just repair-pull runs all mirror pulls (pull-skills, pull-extensions, update-themes) and regenerates the package manifest.

pull-extensions includes pull-pi-deep-review, pull-pi-notify, and pull-pi-system-theme, so nested mirror pulls are included automatically.

Release workflow

Use release automation for version bump propagation + mirror publish + GitHub releases (npm publish is handled by per-repo trusted publisher workflows).

Dry-run first:

just release-dry pi-deep-review minor

Then execute:

just release pi-deep-review minor

Supported targets (canonical package names only):

  • pi-deep-review (bumps pi-deep-review → @ferologics/pi-extensions → pi-shit)
  • pi-notify (bumps pi-notify → @ferologics/pi-extensions → pi-shit)
  • pi-system-theme (bumps pi-system-theme → @ferologics/pi-extensions → pi-shit)
  • @ferologics/pi-extensions (bumps @ferologics/pi-extensions → pi-shit)
  • @ferologics/pi-skills (bumps @ferologics/pi-skills → pi-shit)
  • pi-shit (bumps only root package)

Supported bump levels: patch, minor, major.

Release targets are discovered from piRelease metadata in release manifests, and just check runs release-config-check to fail fast when any release manifest is missing valid piRelease (repo + branch, optional subtreePublishRecipe). npm Trusted Publishers must be configured in npm for each package/repo pair so release-created GitHub releases can publish without OTP.