pair-review

Reviews uncommitted code or branches by dispatching parallel subagents across correctness, tests, design, and agent-pathology concerns.

Updated Apr 3, 2021
One-click install
npx skills add https://github.com/shrik450/dotfiles --skill pair-review-shrik450
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: pair-review
Source: https://github.com/shrik450/dotfiles/tree/main/dot_claude/skills/pair-review
Command: npx skills add https://github.com/shrik450/dotfiles --skill pair-review-shrik450

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you write code with AI agents, subtle issues slip through: unrequested fallbacks, half-finished implementations, tautological tests, and drift from the original goal. This Skill gives you the sanity check a good pairing partner would, before you open a PR. ## Core Features & Use Cases - Parallel specialist review: Dispatches subagents for correctness, tests, design quality, and agent-output pathologies (sycophantic over-delivery, goal drift, CLAUDE.md violations), then synthesizes findings into a terse ranked list. - Adaptive scope and sizing: Reviews uncommitted changes, a feature branch against the default branch, or a custom commit range; collapses to a single agent for small diffs and handles pure-doc diffs inline. - Pairing-voice output: Produces action-oriented findings with path:line citations, ranked by leverage, addressed to you as the author — not a neutral reviewer checklist. - Use Case: After an agent implements a feature across several files, run the skill on your uncommitted work to catch a silently swallowed exception, a missing edge-case test, and an unrequested backwards-compat shim before committing. ## Quick Start Ask the assistant to run pair-review on your current uncommitted changes to get a terse, cited list of findings before you commit.

Frequently Asked Questions about pair-review

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

FAQPage Schema
How do I review code written by AI agents before committing?ā–¼

Run the skill with no arguments to review uncommitted changes, or pass a branch name or commit range. It dispatches parallel subagents covering correctness, tests, design, and agent-specific pathologies, then returns a terse ranked findings list with path:line citations.

What is the difference between pair-review and a PR review skill?ā–¼

Pair-review is author-side: it sanity-checks your own uncommitted work or branch in a direct pairing voice. For reviewing someone else's pull request with a neutral guide tone, use the multi-agent-pr-review skill instead.

Can pair-review check a specific commit range instead of a branch?ā–¼

Yes. Pass a range like HEAD~3..HEAD or abc123..def456 and it diffs that range. Ranges crossing a merge commit trigger a warning but the review still proceeds.

Does pair-review modify my code or post comments to GitHub?ā–¼

No. The skill is strictly read-only: it never edits files, commits, or posts reviews. It outputs findings inline and stops; applying any fix is a separate action you request explicitly.

What kinds of agent-written code problems does it catch?ā–¼

It flags sycophantic over-delivery like unrequested fallbacks and compat shims, half-implementations such as TODOs and dead branches, goal drift where the build diverges from the request, tautological tests, and CLAUDE.md style violations.

What happens when the diff is very small or documentation only?ā–¼

Diffs under 150 lines or 3 files use a single collapsed agent instead of the full parallel pipeline. Pure documentation diffs skip specialists entirely and get an inline clarity and accuracy pass.