About bug-review
Bug review is a code-review skill focused exclusively on correctness issues that block merging. It guides reviewers to inspect changed code, callers, and tests, and to report each confirmed or uncertain issue with a location and reproduction path.
Key features
- 01Focus on merge-blocking correctness
- 02Read changed code, callers, and tests
- 03Include file and line for each issue
- 04Provide failure steps or a test sketch
- 05Preserve the working tree
Use cases
- 01Review a supplied code diff and ticket
- 02Find behavior or error-path regressions
- 03Check for data loss, permission gaps, or races
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/bug-reviewin Claude Code to confirm it loaded.
Details
From the project READMEBug review
Review the diff you were handed, with its contract or ticket if one came along. When you compute the diff yourself, run git fetch origin <base> and diff against origin/<base>: a local base branch can lag the remote and pull unrelated commits in.
Correctness is your only axis. Read the changed code, its callers and its tests; coding standards and style docs belong to the other reviews. Report only issues that block merging: wrong behavior, data loss, permission or tenant holes, races, broken error paths, type holes that reach runtime.
For each issue:
file:line- why it is wrong, in one or two sentences
- how to demonstrate the failure: the input and steps, or a sketch of a test that goes red
Mark every issue you suspect but couldn't confirm, and say where you looked. If nothing blocks merging, say so in one line.
Leave the working tree as you found it: someone else is building in it. Write any repro or demo test outside the repo (under $TMPDIR), or delete it before reporting. The report carries the test sketch.
Completion: every changed hunk read, every reported issue carries all three parts, and git status matches what it showed when you started.