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

@clementprevot/pi-git-editor-guard

v0.1.2

Published

Pi extension that keeps git from opening an editor in the agent's non-interactive shell

Readme

@clementprevot/pi-git-editor-guard

A Pi extension that keeps git from hanging the coding agent on an editor: commands that would open an interactive TTY editor (rebase --continue after a conflict, a bare commit, an interactive rebase, ...) are rewritten in place with GIT_EDITOR=true so git keeps its prepared message and finishes immediately.

Why

Agents manage rebases all the time, and the classic failure is git rebase --continue after resolving a conflict opens the editor (e.g. VIM) to confirm the commit message. In the agent's non-interactive shell that editor either errors out or, worse, just sits there while the agent waits on a command that will never finish. The fix is well known (GIT_EDITOR=true, which overrides core.editor and EDITOR), but it relies on the model remembering it every single time. This guard makes forgetting impossible.

Install

pi install npm:@clementprevot/pi-git-editor-guard

Updates ship with pi update --extensions. The extension applies to your next session (quit and relaunch or issue a /reload command).

How it works

On every bash tool call, the extension:

  1. Splits the command chain into subcommands (respecting quotes and preserving the original separators).
  2. Classifies each one: does this git command open an editor, and is that editor already handled?
  3. When an editor is missing, prefixes the subcommand in place; the rewritten command is what executes and what the session records.

Covered commands

  • git rebase --continue and interactive rebases (-i, --interactive): GIT_EDITOR=true, plus GIT_SEQUENCE_EDITOR=true when the todo list is involved (--edit-todo needs only the sequence editor)
  • git commit without a message flag (-m, -F, --no-edit, -C, ...) or git commit --amend alone
  • git merge, including git merge --continue
  • git cherry-pick --continue and git revert -e
  • git tag -a/-s without -m (git then fails fast with a clear "no tag message" error instead of hanging)
  • git notes without -m

Left alone

  • Commands that already set their own editor: GIT_EDITOR=, GIT_SEQUENCE_EDITOR=, or -c core.editor=.... An explicit choice is respected, even the one that would hang.
  • Any command that is not git, including echo git rebase --continue and comments.

The rewrite is a no-op when git would not have opened an editor anyway (GIT_EDITOR=true on git rebase main changes nothing), so the guard errs on the side of prefixing.

Configuration

None. The rewrite is deterministic, always safe in a non-interactive shell, and needs no user interaction during a rebase.

License

MIT