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-reviews

v1.1.0

Published

CLI and agent skills for managing GitHub PR review comments. List, filter, reply, and watch for bot findings.

Readme

agent-reviews

Manage GitHub PR review comments from the terminal and from AI coding agents.

PR review bots (Copilot, Cursor Bugbot, CodeRabbit, etc.) leave inline comments on your pull requests. agent-reviews gives you a CLI to list, filter, reply to, and watch those comments, plus agent skills that automate the entire triage-fix-reply loop.

Why

gh CLI is fragile for review comments. Agents frequently get the syntax wrong, fail to paginate, and can't reliably detect whether a comment has been replied to. agent-reviews provides a single, purpose-built interface that handles all of this correctly.

Bot reviews create a doom loop. You fix one round of findings, push, and new comments appear. Fix those, push again, more comments. This cycle can eat hours. The included skills solve this with an integrated watcher that keeps fixing and replying until the bots go quiet.

Works in cloud environments. Most solutions rely on local tooling that isn't available in cloud or remote agent environments. agent-reviews works everywhere, so you can kick off a session, let the agent resolve all findings autonomously, and come back to a clean PR.

Install

CLI (npm)

npm install -g agent-reviews

Agent Skills

Three skills are available, each as a slash command (no npm install required):

| Skill | What it resolves | |-------|-----------------| | resolve-reviews | All comments (human + bot) | | resolve-agent-reviews | Bot comments only (Copilot, Cursor, etc.) | | resolve-human-reviews | Human comments only |

Works with any agent that supports Agent Skills (Claude Code, Cursor, Codex, etc.):

npx skills add pbakaus/agent-reviews@resolve-agent-reviews

Replace resolve-agent-reviews with whichever skill you want. Skills use npx agent-reviews at runtime, so the CLI is fetched automatically.

You can also use both: install the CLI globally for direct terminal use, and a skill for the agent workflow.

Authentication

The simplest method is the GitHub CLI. If you're logged in with gh auth login, agent-reviews picks up the token automatically. No configuration needed.

For cloud/remote environments or HTTPS proxy setups, set GITHUB_TOKEN or GH_TOKEN directly. agent-reviews includes undici ProxyAgent support and will route requests through HTTPS_PROXY automatically when set.

Resolution order (first match wins):

  1. GITHUB_TOKEN environment variable
  2. GH_TOKEN environment variable
  3. .env.local in the repo root
  4. gh auth token (GitHub CLI)

Fork pull requests

Branch discovery keeps the head repository separate from the PR's base repository. It uses the branch push remote, remote.pushDefault, tracking remote, or origin (in that order), and looks for the current branch in configured GitHub repositories and the fork's parent/source repositories. The selected remote's push URL determines the head repository, including when its fetch URL points upstream. An upstream remote is not required. A single GitHub remote with another name also works.

GH_REPO=organisation/project restricts the target repository without changing the head owner. Use GH_REPO=organisation/project agent-reviews --pr 123 to select a PR explicitly, including from detached HEAD. Malformed GH_REPO values fail explicitly. If multiple open PRs match, or a matching PR has a deleted/inaccessible head repository that cannot be verified, the CLI asks for an explicit target instead of choosing one. Discovery uses the GitHub API and works with token authentication without requiring gh.

Custom API host

Set GITHUB_API_URL to point agent-reviews at a GitHub Enterprise host or any API-compatible server (useful for testing, recording, or routing through a local mediator). Defaults to https://api.github.com.

# GitHub Enterprise Server
GITHUB_API_URL=https://github.example.com/api/v3 agent-reviews

# Local API-compatible server
GITHUB_API_URL=http://127.0.0.1:8080 agent-reviews

GraphQL endpoint resolution: agent-reviews uses ${GITHUB_API_URL}/graphql by default. For GitHub Enterprise Server, where REST lives under /api/v3 and GraphQL under /api/graphql on the same origin, the trailing /api/v3 is rewritten to /api/graphql automatically. Set GITHUB_GRAPHQL_URL directly if you need full control over the GraphQL endpoint.

CLI Usage

# List all review comments on the current branch's PR
agent-reviews

# Only unresolved comments
agent-reviews --unresolved

# Only unanswered bot comments
agent-reviews --unanswered --bots-only

# Full detail for a specific comment (diff hunk + replies)
agent-reviews --detail 12345678

# Reply to a comment
agent-reviews --reply 12345678 "Fixed in abc1234"
agent-reviews --reply 12345678 --body-file body.md

# JSON output for scripting / AI agents
agent-reviews --json

# Watch for new comments (polls every 30s, exits after 10 min idle)
agent-reviews --watch --bots-only

# Target a specific PR (otherwise auto-detects from branch)
agent-reviews --pr 42

Unknown options, unexpected arguments, and invalid numeric values fail before authentication or network requests. To pass an inline reply starting with a dash, put options first and use agent-reviews --reply 12345 -- "- Fixed the issue". Everything after -- is literal text.

Options

| Flag | Short | Description | |------|-------|-------------| | --unresolved | -u | Only unresolved/pending comments | | --unanswered | -a | Only comments without any replies | | --reply <id> "msg" | -r | Reply to a comment | | --body-file <path> | | Read reply text from a UTF-8 file instead of a positional message | | --resolve | | Resolve the review thread after replying (use with --reply) | | --detail <id> | -d | Full detail for a comment | | --pr <number> | -p | Target a specific PR | | --json | -j | JSON output | | --bots-only | -b | Only bot comments | | --humans-only | -H | Only human comments | | --ignore-author <login> | | Exclude an author from listing and watching; repeat for multiple authors | | --expanded | -e | Show full detail for each listed comment | | --watch | -w | Poll for new comments | | --interval <sec> | -i | Poll interval in seconds (default: 30) | | --timeout <sec> | | Inactivity timeout in seconds (default: 600) |

To hide workflow status comments, use agent-reviews --ignore-author 'github-actions[bot]'. Repeat the flag for multiple authors, including with --watch. Matching is case-insensitive and uses the full GitHub login, including [bot] when present. Excluded authors' top-level findings are hidden, but their replies remain visible as context in other authors' threads. Explicit --detail lookups and replies are unaffected. No authors are excluded by default.

Agent Skills

The skills automate the full PR review resolution workflow:

  1. Fetch unanswered comments (all, bot-only, or human-only depending on skill)
  2. Evaluate each finding (true positive, false positive, actionable, etc.)
  3. Fix real issues and run lint/type-check
  4. Dismiss false positives with an explanation
  5. Reply to every comment with the outcome
  6. Watch for new comments and repeat until quiet
  7. Report a summary of all actions taken

Skill behavior

  • True positives / actionable feedback get fixed and replied with Fixed in {commit}
  • False positives get replied with Won't fix: {reason}
  • Uncertain findings prompt the user for guidance
  • All fixes are batched into a single commit before polling begins
  • Watch mode loops until no new comments appear for 10 minutes

How It Works

Comment types

agent-reviews fetches three types of GitHub PR comments:

| Type | Label | Description | |------|-------|-------------| | Review comment | CODE | Inline comment attached to a specific line | | Issue comment | COMMENT | General PR-level comment | | Review | REVIEW | Review summary (approved, changes requested) |

Meta-comment filtering

Bot review bodies (REVIEW type) are always filtered out since actionable findings come through as inline comments. Additionally, these bot issue comments are filtered:

| Bot | What's filtered | |-----|----------------| | Vercel | Deployment status ([vc]:...) | | Supabase | Branch status ([supa]:...) | | Cursor Bugbot | Review summary ("Cursor Bugbot has reviewed your changes...") | | Copilot | PR review summary ("Pull request overview") | | CodeRabbit | Walkthrough, summary, and "review skipped" comments | | Sourcery | Reviewer's guide and PR summary | | Codacy | Analysis summary and coverage summary | | SonarCloud | Quality Gate pass/fail summary | | Gemini Code Assist | "Summary of Changes" issue comment |

Reply status

Each comment displays its reply status:

| Status | Meaning | |--------|---------| | no reply | No one has replied | | replied | A human has replied | | bot replied | Only bots have replied |

Watch mode

Polls the GitHub API at a configurable interval and reports new comments as they appear. Outputs both formatted text and JSON for AI agent consumption. Exits automatically after a configurable inactivity timeout (default: 10 minutes).

Reply files preserve Markdown and newlines exactly. For multiline or complex replies, write the text to a file and pass --body-file body.md to avoid shell quoting and command substitution. Both absolute and relative paths are supported; relative paths are resolved from the current directory. Prefer uniquely named temporary files outside the repository so later commits cannot accidentally include reply text. Use either a positional message or --body-file, not both; empty or whitespace-only replies are rejected. The flag works with --resolve and --json.

Changelog

1.1.0 (September 10, 2026)

  • Read exact UTF-8 reply text with --body-file, without shell command substitution.
  • Reject unknown flags and invalid arguments before posting; use -- for replies beginning with a dash.
  • Discover fork PRs across upstream repositories, separate push URLs, and GitHub Enterprise hosts.
  • Exclude selected authors from listing and watching with repeatable --ignore-author.
  • Reduce duplicate replies with fresh reply checks and watcher-startup reconciliation in all three skills.
  • Update development dependencies to Vitest 5 and refresh website dependencies and audit fixes.

Development tests now require Node.js 22.12+, 24, or 26+ as supported by Vitest 5. CLI runtime support remains Node.js 18+.

1.0.2

  • GitHub Enterprise Server support via GITHUB_API_URL env var (also works for local API-compatible servers used in testing). REST and GraphQL endpoints both honor it, with GHES /api/v3 automatically rewritten to /api/graphql. Optional GITHUB_GRAPHQL_URL for unusual setups.
  • Gemini Code Assist meta-comment filtering: the bot's ## Summary of Changes issue comment is now dropped, while inline severity-badged findings are preserved.

1.0.0

Three skills instead of one. The single agent-reviews skill has been split into three, each tailored for different workflows:

  • resolve-reviews resolves all comments (human + bot)
  • resolve-agent-reviews resolves bot comments only
  • resolve-human-reviews resolves human comments only

Thread resolution. The new --resolve flag marks GitHub review threads as resolved after replying. Uses the GraphQL resolveReviewThread mutation. Works with --reply in any argument order.

Expanded bot support. Added detection and meta-comment filtering for CodeRabbit, Sourcery, Codacy, SonarCloud/SonarQube Cloud, and Copilot PR reviewer, in addition to the existing Cursor Bugbot, Vercel, and Supabase filters.

Agent-harness universal. Skills now work with any agent that supports Agent Skills (Claude Code, Cursor, Codex, etc.), not just Claude Code.

Watch mode improvements. The watcher now exits immediately when new comments are found (with a 5s grace period for batch posts), designed for loop-based workflows where the agent processes comments and restarts the watcher.

New CLI options:

  • --resolve resolves the review thread after replying (use with --reply)
  • --expanded / -e shows full detail (body, diff hunk, replies) for each comment in list mode

Bug fixes:

  • --json --resolve no longer emits plain-text status messages to stdout

Cloud and proxy support:

  • GH_TOKEN environment variable support (in addition to GITHUB_TOKEN)
  • GH_REPO environment variable for targeting repos in detached environments
  • Curl-based HTTP fallback for environments without native fetch/undici
  • Curl requests include timeouts (10s connect, 60s max)

Smarter filtering. Bot review bodies (summaries listing inline findings) are now automatically excluded, since actionable findings always come through as inline comments. Reply comments posted by agent-reviews itself (> Re: comment ...) are also filtered to avoid noise.

Simplified architecture. Skills now invoke npx agent-reviews at runtime instead of bundling their own scripts, reducing the package from ~4000 lines of duplicated code to a single CLI entry point. Skills no longer run redundant startup commands (version check, branch detection, PR lookup), relying on the CLI's own error handling instead.

License

MIT