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-git-context

v0.1.3

Published

Opinionated git state context injection for pi

Readme

pi-git-context

npm

Opinionated git state context injection for pi.

What it does

Injects a concise, current git snapshot into the LLM context on every prompt, while keeping the session history clean by only persisting snapshots when state actually changes.

Snapshot contents

| Section | Condition | Example | |---------|-----------|---------| | Remote | If remote exists | Remote: github.com/h14h/pi-packages | | Default branch | If determinable, and not current branch | Default branch (main, a1b2c3d): synced with origin | | Current branch / HEAD | Always in repo | Branch: feat/auth-refactor (b2c3d4e), +3 commits from main, ahead 1 / behind 0 | | PR status | If gh CLI available and branch has PR | PR: #42 (Ready) | | Worktrees | If linked worktrees exist | Linked worktrees: 6 total | | Working tree | Always | Working tree: dirty (2M, 1S, 1U, 0D) | | Primary worktree | If CWD is a linked worktree | Primary worktree (main, a1b2c3d): synced with origin, clean |

Abbreviations: M = modified, S = staged, U = untracked, D = deleted.

Footer status

A persistent footer segment shows:

◈ ● (a1b2c3d) ✓
  • = linked worktree (· = primary worktree, fixed-width)
  • = clean / = dirty / = conflicted
  • (a1b2c3d) = short SHA
  • = snapshot up to date / ? = warning / Braille spinner = refreshing

Commands

| Command | Description | |---------|-------------| | /git | Open a read-only overlay showing the exact snapshot the agent will see on the next turn |

How it works

  • Before each agent loop: computes snapshot. If it changed from the last persisted snapshot, a new custom_message entry is appended to the session (visible in TUI, collapsible).
  • Before every LLM call: the context handler strips all prior git snapshots and injects exactly one fresh, ephemeral snapshot. The LLM never sees stale state.
  • After each agent turn: if write, edit, or bash tools ran, an optimistic background refresh is kicked off so the next prompt sees current state.
  • Cache: a quick fingerprint (branch + SHA + worktree path + dirty count) avoids recomputing the full snapshot when nothing changed.

Install

pi install ./packages/pi-git-context

Or from npm (once published):

pi install pi-git-context