A pull-request review workflow focused on finding correctness problems, such as logic errors, edge cases, and security issues. A pull request is a proposed set of code changes for review before it is merged.

Use it to review a GitHub pull request or code changes, post inline comments, optionally create fixes, and track whether reported problems are resolved.

It provides several independent review passes and validates their findings, helping catch bugs that one review might miss.

bug-review — Skill for Claude Code and Codex by pproenca: A pull-request review workflow focused on finding correctness problems…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/pproenca/dot-skills/bug-review

Any agent

npx skills add pproenca/dot-skills --skill bug-review

Clone the repo

git clone --depth 1 https://github.com/pproenca/dot-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/pproenca/dot-skills/bug-review.svg)](https://agentmods.dev/skills/pproenca/dot-skills/bug-review)

Your own site

<a href="https://agentmods.dev/skills/pproenca/dot-skills/bug-review"><img src="https://agentmods.dev/badge/skills/pproenca/dot-skills/bug-review.svg" alt="Measured on agentmods" height="20"></a>

Per session 136 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,100 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00136	$0.02100
Opus 5	$0.00068	$0.01050
Sonnet 5	$0.00027	$0.00420
Haiku 4.5	$0.00014	$0.00210

Measured 5d ago against content hash 8b8f26ce2a8e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bug-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

The scan reads SKILL.md. This mod also ships 10 executable files (scripts/classify-resolutions.sh, scripts/dedup.sh, scripts/fetch-pr.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/bug-review/SKILL.md · 216 lines

How it starts

The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Bug Review v2

Multi-pass PR review agent with 5 parallel review passes, majority voting, independent Opus validation, and resolution rate learning. Posts inline PR comments and optionally generates autofix commits. Tracks whether findings get resolved at merge time and uses that signal to improve future reviews.

When to Apply

User asks to review a pull request for bugs or correctness issues
User runs /bug-review <PR-number-or-URL>
User runs /bug-review:resolve <PR> to classify resolutions after merge
User runs /bug-review:report for resolution rate statistics
User asks for code review focused on logic errors, edge cases, or security
User wants to find bugs in a diff or set of changes

Setup

On first run, verify:

gh CLI is installed and authenticated (gh auth status)
Current directory is a git repo with a GitHub remote
jq is installed (for JSON processing)
bc is installed (for resolution rate calculations; pre-installed on most systems)

Read config.json for configuration (passes, vote threshold, models, category weights).

Workflow Overview

/bug-review <PR>
  |
  v
Fetch PR context + gather-context.sh
  |
  v
5 parallel passes (shuffled diffs, Sonnet) --> Aggregate & vote (3/5 majority)
  |
  v
Independent Opus validator --> Dedup --> Present findings --> Post + store
  |
  (later, after merge)
  v
/bug-review:resolve <PR> --> Classify resolutions --> Update category weights

Command: /bug-review

Step 1: Parse Input & Fetch Context

Parse the PR identifier (number, URL, or branch name)
Check cache: Look for ${CLAUDE_PLUGIN_DATA}/bug-review/cache/pr-{N}/ — if cache exists for the same head commit, offer to resume from the last checkpoint
Run scripts/fetch-pr.sh <pr-identifier> to get PR diff + metadata as JSON
Save the diff to a temp file for shuffling
Run scripts/gather-context.sh <changed-files-json> to get prioritized context (callers, types, tests, repo rules)
Read .bug-review.md from repo root if it exists
Save checkpoint: Write context to ${CLAUDE_PLUGIN_DATA}/bug-review/cache/pr-{N}/context.json

Read the full file on GitHub · 216 lines

Files

What ships with it

16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

5d ago First seen · 216 lines · 136 tokens per session scan A 8b8f26ce2a8e

Subscribe to this mod's changes

bug-review is a skill published in the GitHub repository pproenca/dot-skills (202 stars, last pushed 20d ago), licensed MIT. It adds 136 tokens to every session and 2,100 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Code review

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens