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

agent-commit

v0.2.0

Published

Reader and query tool for agent-commit formatted git history

Readme

agent-commit

Reader, query tool, and setup helper for the agent-commit format: a normal commit subject plus an optional, single-line Agent-Context: {json} git trailer that captures the reasoning an AI coding agent already has at commit time, so the next agent (or human) doesn't have to re-derive it from the diff. Full format spec, rationale, and the AGENTS.md block to adopt it in a project: github.com/AngelCodes95/agent-commit.

Reading the format back never actually requires this CLI, plain git log with a trailer format string does it (see the main repo's SPEC.md, "Reading it back"). This package adds structured filtering, an advisory check, and a deterministic setup command on top of that.

Install

npm install -g agent-commit

Or run it without installing: npx agent-commit <command>.

Installing directly from the git repository (npm install git+https://github.com/AngelCodes95/agent-commit.git) does not currently work and isn't recommended: this package lives in a subdirectory (cli/), not the repository root, and npm's subdirectory-install support (gitSubdir) only just landed in pacote and isn't in most installed npm versions yet; on top of that, current npm disables git-type installs by default entirely (EALLOWGIT). Verified directly against the real, pushed URL, not assumed. Use the registry install above.

Commands

agent-commit init [directory] Writes the AGENTS.md block a repo needs to adopt the format into the target directory (the current directory if none is given), and links CLAUDE.md to it unless --no-claude-code is passed. Refuses to touch an existing, unrelated commit-message convention or an already-set-up repo without --force/--update.

agent-commit log [--breaking] [--grep <text>] [--refs <ref>] [--touches <path>] [--since <date>] [--until <date>] [--json] Filters commit history by Agent-Context fields. --grep is a case-insensitive substring match against why, not semantic search. --refs is an exact match, see the main repo's SPEC.md for why ref form consistency matters. --touches matches whole path segments in both directions: src/auth finds src/auth, src/auth/session.ts, and the broader src, but never src/authz.

agent-commit show <ref> [--json] Shows a single commit's Agent-Context trailer.

Every result from log, show, blame, and check includes the commit's hash: hash (full) and shortHash (git's own abbreviation) in --json output, and the short hash at the start of each entry in text output.

agent-commit blame <file> [-L <start>[,<end>]] [--json] Shows the Agent-Context of each commit that last changed the given lines (the whole file without -L), via git blame, with the line ranges each commit owns. -L takes git's numeric form, 1-based and inclusive: -L 42 or -L 40,60. Lines not committed yet are counted on stderr rather than attributed to anything.

agent-commit check [--range <range>] [--count <n>] [--json] Read-only, advisory report on whether recent commits have a usable trailer. Distinguishes a commit with no trailer at all from one where an Agent-Context: line exists in the message but wasn't recognized as a trailer (MISPLACED), which is what a mishandled squash-merge produces. Never writes anything.

agent-commit merge-draft <range> [--json] Deterministically unions touches/refs/breaking across a range of commits and lists each one's raw why as a candidate, for composing a squash-merge commit's trailer by hand. Never synthesizes a why.

agent-commit --version

What this deliberately doesn't do

No semantic or meaning-based search, --grep is literal substring matching. No mandatory schema, no enforcement by default, check is advisory and never blocks. Both are intentional, not unfinished, see the main repo's SPEC.md and CONTRIBUTING.md.

License

Apache License 2.0. See LICENSE.