branch-review

Reviews all unmerged branch changes against master with deletion-biased structural and correctness passes.

3|Updated Aug 3, 2026
One-click install
npx skills add https://github.com/gen4recomp/gen4recomp --skill branch-review-gen4recomp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: branch-review
Source: https://github.com/gen4recomp/gen4recomp/tree/main/.agents/skills/branch-review
Command: npx skills add https://github.com/gen4recomp/gen4recomp --skill branch-review-gen4recomp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Branches accumulate unmerged commits that need a rigorous, fresh-context review before merging, and implementation agents often miss structural duplication, speculative abstractions, weak tests, and subtle correctness bugs in their own work. ## Core Features & Use Cases - Full-scope branch review: Derives the complete unmerged diff from git merge-base, reads entire changed files, and inspects every commit message for policy violations. - Multi-pass methodology: Runs premise validation, structural shape, per-file organization, function-level, test-quality, simplification, and adversarial correctness passes in order. - Direct fixing and verification: Fixes established issues in place, then runs lint and the full test suite before reporting, plus a prevention retrospective on guidance gaps. - Use Case: Before merging a feature branch, dispatch this review to get a fresh-reader audit that cuts speculative abstractions, reconciles spec acceptance scenarios against tests, and reports net line delta with honest verification status. ## Quick Start Ask the agent to review all unmerged changes on the current branch using the branch-review skill and fix any established issues directly.

Frequently Asked Questions about branch-review

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

FAQPage Schema
How do I review all unmerged changes on a git branch before merging?

Use git merge-base to find where the branch diverged from master, then diff and read every changed file in full rather than only hunks. This skill automates that scoping and runs structured review passes over the complete branch.

What does a deletion-biased code review check for?

It challenges whether each new file, abstraction, helper, and compatibility branch earns permanent existence by naming a current consumer and invariant. Speculative complexity is removed unless evidence justifies keeping it.

Can this review fix issues instead of only reporting them?

Yes, established issues are fixed directly in small edits with focused tests, and only decisions genuinely requiring human judgment are left open. Final lint and full test suite runs are reported truthfully.

Does the review validate spec acceptance scenarios against tests?

For spec-driven branches, every acceptance scenario in the finalized deliverables is independently reconciled against tests at HEAD. Scenarios that are missing, weakened, or bypass required production composition are treated as unsatisfied.

What are the limitations of an automated branch review?

It cannot resolve design choices that genuinely require human judgment, and ROM-gated or capability-blocked verification is reported as blocked evidence rather than passed. It also does not edit guidance during the review.