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-annotated-reply

v0.3.7

Published

Annotated reply workflow for pi (model responses and file sources)

Vulnerabilities

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

Links

Git

Maintainers

omaclomacl

Keywords

pi-package

Readme

pi-annotated-reply

Adds an annotated-reply workflow to pi. Construct prompts by annotating either the last model response or a file. Annotated text is loaded into pi’s main editor, ready to submit as your next prompt. Source files are never modified.

Commands

| Command | Description | |---------|-------------| | /reply | Annotate the last model response | | /reply <path> | Annotate a file (original file is not changed) | | /reply --raw | Load raw content into editor without annotation header | | /reply --diff | Wrap content in a diff fenced block before loading | | /reply-editor | Same as /reply, but opens in your external editor ($VISUAL/$EDITOR) | | /reply-editor <path> | Same as /reply <path>, but opens in your external editor | | /load-content | Alias for /reply --raw | | /load-content <path> | Alias for /reply <path> --raw | | /load-content-editor | Alias for /reply-editor --raw | | /load-content-editor <path> | Alias for /reply-editor <path> --raw | | /reply-diff | Alias for /reply --diff | | /reply-diff-editor | Alias for /reply-editor --diff | | /annotated-reply | Alias for /reply | | /annotated-reply <path> | Alias for /reply <path> | | /annotated-reply-editor | Alias for /reply-editor | | /annotated-reply-editor <path> | Alias for /reply-editor <path> | | /annotated-reply-diff | Alias for /reply-diff | | /annotated-reply-diff-editor | Alias for /reply-diff-editor |

All commands accept:

  • --raw to skip the annotation header and load bare content into the editor.
  • --diff to wrap source content in a fenced diff block. This is useful for syntax-highlighted previews in tools that render fenced code blocks.

Prefill format

The extension prefills content like:

annotated reply below:
original source: last model response
annotation syntax: [an: your note]

---

<model response content>

or

annotated reply below:
original source: file ./path/to/file.ts
annotation syntax: [an: your note]

---

<file content>

Annotation style (suggested)

A simple default is [an: your note], inline with the source text.

This is only a suggested pattern, not a strict format. Use whatever annotation style is clear for your workflow.

Install

pi install npm:pi-annotated-reply

Or from git:

pi install https://github.com/omaclaren/pi-annotated-reply

Or run directly:

pi -e https://github.com/omaclaren/pi-annotated-reply

Notes

  • If $VISUAL/$EDITOR is not set, *-editor commands automatically fall back to pi's built-in extension editor.
  • If the latest assistant message is incomplete or has no text content, reply-based commands show a warning.
  • File annotation reads the selected file content and injects an editable copy into the editor. The source file is never modified by this extension.

License

MIT