
Security News
TC39 Advances Temporal to Stage 4 Alongside Several ECMAScript Proposals
TC39’s March 2026 meeting advanced eight ECMAScript proposals, including Temporal reaching Stage 4 and securing its place in the ECMAScript 2026 specification.
agent-reviews
Advanced tools
CLI and agent skills for managing GitHub PR review comments. List, filter, reply, and watch for bot findings.
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.
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.
npm install -g agent-reviews
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.
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):
GITHUB_TOKEN environment variableGH_TOKEN environment variable.env.local in the repo rootgh auth token (GitHub CLI)# 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"
# 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
| Flag | Short | Description |
|---|---|---|
--unresolved | -u | Only unresolved/pending comments |
--unanswered | -a | Only comments without any replies |
--reply <id> "msg" | -r | Reply to a comment |
--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 |
--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) |
The skills automate the full PR review resolution workflow:
Fixed in {commit}Won't fix: {reason}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) |
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 |
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 |
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).
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 onlyresolve-human-reviews resolves human comments onlyThread 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 modeBug fixes:
--json --resolve no longer emits plain-text status messages to stdoutCloud and proxy support:
GH_TOKEN environment variable support (in addition to GITHUB_TOKEN)GH_REPO environment variable for targeting repos in detached environmentsSmarter 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.
MIT
FAQs
CLI and agent skills for managing GitHub PR review comments. List, filter, reply, and watch for bot findings.
The npm package agent-reviews receives a total of 990 weekly downloads. As such, agent-reviews popularity was classified as not popular.
We found that agent-reviews demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
TC39’s March 2026 meeting advanced eight ECMAScript proposals, including Temporal reaching Stage 4 and securing its place in the ECMAScript 2026 specification.

Research
/Security News
Since January 31, 2026, we identified at least 72 additional malicious Open VSX extensions, including transitive GlassWorm loader extensions targeting developers.

Research
Six malicious Packagist packages posing as OphimCMS themes contain trojanized jQuery that exfiltrates URLs, injects ads, and loads FUNNULL-linked redirects.