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

@johnhof/arbiter

v1.0.7

Published

Browser-based git diff review UI with inline commenting and agent prompt export

Readme

Arbiter

Vibe Coded Tests Coverage

Browser-based git diff reviewer with inline commenting and real-time agent integration. Review branch diffs GitHub-style, leave comments on specific lines or files, then export all comments as a structured markdown prompt for an AI agent to apply the fixes.

Arbiter Screenshot

Installation

npm install -g @johnhof/arbiter

This installs arbiter as a global command. Verify with which arbiter.

Usage

arbiter

Opens at http://localhost:7429 (auto-increments if taken). Defaults to the git root of the current working directory.

CLI Flags

| Flag | Description | Default | |------|-------------|---------| | --path /path/to/repo | Repository to diff | git root of CWD | | --port <number> | Server port (auto-increments if taken) | 7429 | | --export <mode> | Default export button: clipboard, file, or accept | clipboard |

Features

  • Branch comparison — select source and target branches from any local git repo
  • Unified diff view — syntax-highlighted, with expandable hidden context lines
  • Three comment levels — overall diff, per-file, and inline (line or range selection via click/shift-click/drag)
  • Comment navigation — fixed widget with prev/next jumping and Clear All
  • Agent prompt export — copy to clipboard, download as markdown, or accept for agent polling
  • Agent connection status — live indicator showing whether an agent is listening
  • Generated file detection — respects .gitattributes patterns to collapse generated/binary files

Claude Code Skill

Arbiter ships with a Claude Code skill at .claude/skills/arbiter/ that automates the review loop: Claude generates an Arbiter link, the user reviews and leaves comments, then clicks Accept. Claude polls for the prompt and applies the changes.

Install the skill

Option 1: Register the skill directory in your Claude Code settings (~/.claude/settings.json for global, or .claude/settings.json for per-project):

{
  "skills": ["<path-to-arbiter>/.claude/skills"]
}

Option 2: Symlink into a project's existing skills directory:

ln -s <path-to-arbiter>/.claude/skills/arbiter .claude/skills/arbiter

Option 3: Copy the skill directory into your project. Create .claude/skills/arbiter/SKILL.md with the contents from the Arbiter repo:

your-project/
└── .claude/
    └── skills/
        └── arbiter/
            └── SKILL.md    # Copy from <path-to-arbiter>/.claude/skills/arbiter/SKILL.md

Find your install path with npm ls -g arbiter or which arbiter.

Use the skill

In Claude Code, invoke the skill with /arbiter or describe what you want:

/arbiter
review my changes before I merge
let me review the diff on feature-branch

Claude generates an Arbiter link pre-loaded with the right repo and branches, then polls for your review. Open the link, leave comments, click Accept Prompt, and Claude picks them up automatically.

Auto-start the server

To have the Arbiter server start automatically when Claude Code opens a session, add a SessionStart hook to your project's .claude/settings.json:

{
  "hooks": {
    "SessionStart": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "arbiter",
            "async": true,
            "timeout": 10
          }
        ]
      }
    ]
  }
}

This runs arbiter in the background at session start. The server auto-detects the repo path and picks an available port (default 7429). Since async is true, it won't block Claude from starting.

If you need to pass flags (e.g., --export accept), use the full command:

"command": "arbiter --export accept"

Arbiter must be installed globally (npm install -g .) for the hook to find it.

Testing

npm test                                    # Run all tests
npm run test:ui                             # Interactive UI mode
npx playwright test tests/api.spec.js       # Specific file
npx playwright test -g "inline comment"     # By name
npx playwright test --headed                # Visible browser

Tests start their own server automatically — no manual setup needed.

Architecture

Single-page app with no build step. Express backend wraps git CLI commands; vanilla JS frontend handles rendering and comment management. See AGENTS.md for the full design reference.