review

Reviews pull requests by diffing against main and verifying findings with real test suites.

3|3|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/PioneerAIAcademy/cowork-genealogy --skill review-pioneeraiacademy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/PioneerAIAcademy/cowork-genealogy/tree/main/.claude/skills/review
Command: npx skills add https://github.com/PioneerAIAcademy/cowork-genealogy --skill review-pioneeraiacademy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pre-merge code review often rubber-stamps PRs based on green CI on the branch head, missing failures that only appear after merging with main, stale approvals, and checks that cannot actually fail. This Skill performs a rigorous, read-only pre-merge review that proves every finding by running the real suites. ## Core Features & Use Cases - Merge-aware diffing: Diffs the branch against the merge-base with main in a dedicated git worktree, test-merges when behind, and handles fork PRs via gh pr diff fallback. - Verified findings: Runs vitest, tsc, turbo, and pytest suites, watches new lints fail by breaking them deliberately, and scores every finding 1-10 with quoted file:line evidence. - Review governance: Detects open review rounds, unresolved threads, stale approvals by comparing review commit IDs to headRefOid, CODEOWNERS gaps, and incorrect issue-closing links. - Use Case: Before merging PR #1219, run the review to discover it passed 261/261 tests on its own head while a lint it added goes red against main, then receive structured edit suggestions to post in your own words. ## Quick Start Ask the assistant to review PR 1219 before merging and report any findings verified against the actual test suites.

Frequently Asked Questions about review

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

FAQPage Schema
How do I review a GitHub PR before merging?▼

Run the review with a PR number to read the PR body and CI checks, diff the branch against the merge-base with main in a worktree, and apply a structural checklist. Every finding is verified by running the actual test suites rather than assumed from reading code.

Why review the merge with main instead of the branch head?▼

A branch behind main can be green on its own head and red once merged. The skill test-merges origin/main into the worktree before trusting any suite result, catching failures like lints that only break against the newer main.

Can this skill edit code or merge the PR?▼

No, the review is strictly read-only. It never edits the branch, commits, pushes, or merges; every finding is written out as a verbatim you-wrote/change-it-to diff for the author to apply and for you to post in your own words.

How are stale approvals on a PR detected?▼

Each review's commit_id is compared against the PR's headRefOid. Because the repository ruleset does not dismiss stale reviews on push, an approval that read an older commit still clears the merge gate, so every approval is re-checked against the current code.

When does the review stop instead of reporting findings?▼

The review stops when a prior reviewer's latest standing is CHANGES_REQUESTED or any review thread is unresolved, since a second review on an unanswered round duplicates findings. It also escalates schema, auth, ADR, or hard-to-undo changes to the lead.

What are the limitations of the short review pass?▼

The short pass applies only when a PR changes under 50 lines and every path is documentation, skipping the worktree, test-merge, and suite runs. Anything unclear defaults to the full pass, and skipped verification is always disclosed in the report.