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

claude-debrief

v0.1.0

Published

Captures your Claude Code sessions and turns them into rich PRs — with an agent performance evaluation before you add reviewers.

Readme

claude-debrief

Captures your Claude Code sessions and turns them into rich PRs — with an agent performance evaluation before you add reviewers.

How it works

  • A Stop hook captures every Claude Code session as compressed markdown to ~/.claude-debrief/sessions/
  • The /debrief slash command reads all sessions for the current branch, synthesizes a PR description from the reasoning in those sessions (not just the diff), creates or updates the GitHub PR, then prints an agent evaluation to the terminal

Install

npm install -g claude-debrief

Then initialise in each project you want to use it in:

claude-debrief init

init does four things:

  1. Creates .claude-debrief/debrief-template.md — edit to fit your project
  2. Creates .claude-debrief/evaluation-prompt.md — edit to tune the evaluation
  3. Creates .claude/commands/debrief.md — the /debrief slash command
  4. Registers the Stop hook in .claude/settings.json

Usage

Work with Claude Code as normal — sessions are captured automatically.

When you're ready to open a PR, run inside a Claude Code session:

/debrief

Claude will:

  1. Read all sessions for the current branch from ~/.claude-debrief/
  2. Synthesize a PR description using your template (before/after behavior, decisions, references)
  3. Create or update the GitHub PR via gh
  4. Print an agent evaluation to the terminal — review it before adding reviewers

Configuration

Both files are created by init and are meant to be edited and committed:

| File | Purpose | |------|---------| | .claude-debrief/debrief-template.md | Shape of the PR description | | .claude-debrief/evaluation-prompt.md | How to evaluate agent sessions |

Agent evaluation

The evaluation is printed to the terminal after the PR is created — not posted to GitHub. It's a prompt to reflect before handing off to reviewers:

## Agent Evaluation  47/60

| Dimension    | Score |
|--------------|-------|
| Environment  | 8/10  |
| Instructions | 7/10  |
| Navigation   | 9/10  |
| Contract     | 9/10  |
| Tests        | 6/10  |
| Verification | 8/10  |

**Before you add reviewers**
- Run pnpm lint — not run this session despite CLAUDE.md guidance

**Suggested improvements**
- Add a "one logical change per commit" rule to CLAUDE.md

Session storage

Sessions are stored at ~/.claude-debrief/sessions/<workspace>/<branch>/<session-id>.md and cleaned up automatically after 30 days.