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

@anton-kochev/pi-skills

v0.2.0

Published

Anton Kochev's pi skills and prompt commands.

Readme

@anton-kochev/pi-skills

npm version

Anton Kochev's pi skills and prompt commands.

Use /plan when you want the agent to explore before asking questions, reach explicit shared understanding, write a PLAN.md, and only then implement.

Use /commit to stage relevant files when intent is clear and generate a Conventional Commits 1.0.0 message — problem-framed subjects, subject-only by default, with a body only when it earns its place.

Use /srs to create an ISO/IEC/IEEE 29148:2018 Software Requirements Specification with EARS requirements, explicit approval gating, and a traceability matrix.

Use the tdd skill when you want the agent to build or change non-trivial logic test-first with the red-green-refactor loop.

Install

pi install npm:@anton-kochev/pi-skills

For local development from this repository:

pi install -l ./pi-skills

Usage

Invoke prompt commands directly:

/plan <your task>
/commit [instructions]
/srs <product or change description>

These are prompt templates, so they are manual-only: they appear as slash commands rather than being auto-selected as skills.

The TDD workflow is packaged as a skill. Pi can load it proactively for matching requests, or you can force it with:

/skill:tdd <your task>

Changelog

0.2.0

  • /commit: infer and stage relevant files when commit intent is clear, while preserving staged-only commits and avoiding local artifacts.

0.1.3

  • Fix /plan prompt command discovery by quoting its YAML frontmatter description.

0.1.2

  • Add /srs prompt command for ISO/IEC/IEEE 29148:2018 SRS generation with EARS requirements and traceability.

0.1.1

  • /commit: reconcile the subject-mood rule with the problem-framed examples (declarative when stating a problem, imperative when describing value), default to subject-only bodies, and fix an over-length breaking-change example.

0.1.0

  • Initial release: /plan and /commit prompt commands plus the tdd skill.