peer-review

Reviews diffs, branches, files, or PRs and returns severity-ranked findings with suggested fixes.

Updated May 25, 2026
One-click install
npx skills add https://github.com/DATA-AI-XYZ/Tandem --skill peer-review-data-ai-xyz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: peer-review
Source: https://github.com/DATA-AI-XYZ/Tandem/tree/main/skills/peer-review
Command: npx skills add https://github.com/DATA-AI-XYZ/Tandem --skill peer-review-data-ai-xyz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code changes often merge without an independent second look, letting correctness bugs, security holes, and missing tests slip through. This Skill performs a structured peer review of an explicitly scoped target and returns severity-ranked findings so nothing ships unexamined. ## Core Features & Use Cases - Six-dimension review: Examines correctness, security, performance, maintainability, test coverage, and error paths for every change. - Three-level severity ranking: Classifies each finding as blocker, major, or minor, each with a concrete suggested fix, and emits a BLOCK / APPROVE-WITH-CHANGES / APPROVE-WITH-NITS verdict. - Durable HTML artefact: Writes an R15b-conformant AI-CODE-REVIEW report to 41-Reports/reviews/ that feeds the Definition-of-Done R14 gate in close-out-story. - Use Case: Before merging a feature branch, ask for a review of the branch delta; receive a verdict, ranked findings with file:line citations, and a saved HTML report the DoD gate can verify. ## Quick Start Ask the assistant to peer review the current branch's diff against main and report any blocker or major findings with suggested fixes.

Frequently Asked Questions about peer-review

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

FAQPage Schema
How do I review a git diff or branch before merging?

Point the review at an explicit target: a working-tree diff, a branch delta against its merge base, specific file paths, or a PR number. The review covers six dimensions and returns blocker, major, and minor findings, each with a suggested fix and a final verdict.

Can I review a GitHub pull request automatically?

Yes. Provide the PR number and the diff is pulled via gh pr diff, with gh pr view supplying title and intent. Findings are reviewed against what the change is supposed to do, not just what it does.

What severity levels does a code review report use?

Findings are ranked into exactly three levels: blocker (must fix before merge), major (fix or record a deferral decision), and minor (non-blocking). Any blocker produces a BLOCK verdict and fails the DoD R14 gate.

What happens if I don't specify what to review?

The scope is derived from repo state, preferring the working-tree diff then the current branch's delta. If no unambiguous target exists, the review stops and asks which diff, branch, file, or PR to examine rather than guessing.

Does the peer review modify my code?

No. The review is read-only over the code and produces findings only. Fixing is delegated to a separate development step, and every finding includes a concrete suggested fix to hand off.