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

@houserules/plugin-changesets

v0.2.2

Published

houserules plugin: changesets integration (canonical changelog) and the optional per-commit changelog ledger.

Readme

@houserules/plugin-changesets

npm

An agent that finishes a change and stops there leaves nothing behind for the next release. Nobody remembers three weeks later which package a fix touched or what to write in the changelog, and by then the diff is gone from context too.

This plugin wires changesets into the agent's own workflow: a script that authors a changeset the same way changeset add would, a skill and an agent that do it after a completed change, and a Stop hook that nudges when package source changed with no changeset alongside it.

Install

pnpm add -D @houserules/plugin-changesets
pnpm exec houserules init

Requires @houserules/cli. init is what writes the modules into .claude/. The changesets module is on by default in a monorepo, or when .changeset/ already exists.

Modules

  • changesets installs changeset-write.mjs, a non-interactive changeset author for agents. It validates package names against the actual workspace, then writes through the repo's own @changesets/write, the same writer changeset add uses. That library is required: if it is not resolvable from the repo root, the script exits with the install command instead of hand-rolling a file. --empty records "no release needed", and --absorb folds one or more pending changesets into an amended one.

    It also installs changeset-check.mjs, a Stop hook that nudges when package source changed with no changeset recorded for it. The hook exits 2 on purpose when it fires: a non-zero exit is how a Stop hook tells Claude Code to keep going rather than end the turn, so the agent sees the nudge and can act on it in the same turn instead of losing the context. Every other path, including any internal failure, exits 0, so the hook can never break a session. It seeds .changeset/config.json when the repo has none, and writes the /changeset skill plus the changeset-condense skill and the changeset-writer agent (haiku).

    If .changeset/config.json is missing after install, or @changesets/cli is not a devDependency, houserules doctor reports it.

  • ledger is optional and off by default. It installs package-changelog.mjs, which writes a per-commit JSONL changelog to .claude/changelogs/, plus a template for instantiating an archivist agent per target. It exists for repos that want commit-granular history alongside changesets, not instead of them. .claude/changelogs/ never collides with the CHANGELOG.md that changeset version owns, because changesets is still the canonical changelog. See @houserules/cli's README for why.

Upgrading from the CLI core

changesets and ledger were built-in CLI modules. A repo that recorded either before the split gets a HouseError on its next init or update naming this package. Installing it and adding it to the plugins array in .claude/houserules.config.json restores both modules and their files. Nothing is deleted in the meantime.

Part of houserules

houserules is a portable set of Claude Code infrastructure that keeps the agent's context lean. This is one of twelve first-party plugins. The package list has the rest.

License

MIT. See LICENSE.