peer-review

Reviews pending code changes via a read-only reviewer subagent and fixes findings iteratively.

64|11|Updated May 24, 2026
One-click install
npx skills add https://github.com/AlexanderMattTurner/agent-glovebox --skill peer-review-alexandermattturner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: peer-review
Source: https://github.com/AlexanderMattTurner/agent-glovebox/tree/main/.claude/skills/peer-review
Command: npx skills add https://github.com/AlexanderMattTurner/agent-glovebox --skill peer-review-alexandermattturner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Self-reviewing your own code changes is biased by author intent, so defects slip through before a PR is opened. This Skill delegates the diff to a separate read-only reviewer agent, triages the findings, fixes valid issues, and re-reviews until the pass is clean. ## Core Features & Use Cases - Unbiased Diff Review: Captures the branch diff or uncommitted changes plus recent commit history, then passes them to a read-only code-reviewer subagent that cannot be influenced by the author's intent. - Triage and Fix Loop: Classifies each finding as Blocker, Should-fix, Nit, or Invalid, fixes valid issues, reruns tests and lint, and never weakens tests to silence a finding. - Fixed-Point Re-Review: Launches fresh review passes on the updated diff, capped at three passes, and reports anything deliberately deferred. - Use Case: Before opening a PR, ask for a review of your branch; the Skill flags an off-by-one error and duplicated logic, fixes both, reruns the test suite, and confirms a clean second pass. ## Quick Start Ask the assistant to peer review your current branch changes before opening a pull request.

Frequently Asked Questions about peer-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get an unbiased code review of my changes before a PR?

Ask for a peer review of your branch or uncommitted changes. The Skill computes the diff against the base ref, passes it to a read-only code-reviewer subagent, then triages and fixes the findings before re-reviewing.

How does the peer review workflow handle reviewer findings?

Each finding is triaged as Blocker, Should-fix, Nit, or Invalid. Valid issues are fixed with tests and lint rerun, cheap nits are applied, and invalid findings are skipped with a one-line justification. Tests are never weakened to dismiss a finding.

When should I not use a peer review pass on my diff?

Skip it for trivial edits like typo fixes or single-line config tweaks, and do not use it to create a PR end-to-end since the pr-creation workflow already runs its own critique loop.

How many review passes does the peer review loop run?

The loop re-reviews after each round of fixes because fixes can introduce new bugs, stopping when a full pass returns nothing actionable. It is capped at three passes, after which remaining findings are summarized in the report.

Why does the reviewer subagent need the diff passed in the prompt?

The code-reviewer agent is read-only with only Read, Grep, and Glob tools and no shell access, so it cannot run git commands itself. The diff and recent commit history for changed paths must be supplied directly in the prompt.