skills.rest
DoctorMozg
DoctorMozgCOMMUNITY
Explore all skills by this author →
GitHub

review-branch

Reviews all changes on the current git branch against a base branch using a two-wave agent analysis.

2|Updated Apr 4, 2026
Search Tags:#git#diff analysis#code review#agent#branch#adversarial review#pre-pr
One-click install
npx skills add https://github.com/DoctorMozg/claude-pipelines --skill review-branch-doctormozg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-branch
Source: https://github.com/DoctorMozg/claude-pipelines/tree/main/plugins/mz-dev-git/skills/review-branch
Command: npx skills add https://github.com/DoctorMozg/claude-pipelines --skill review-branch-doctormozg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing an entire feature branch by hand is slow and prone to confirmation bias, so critical bugs, security gaps, and missing tests slip through before a pull request is opened. ## Core Features & Use Cases - Two-wave branch review: Wave A runs a 5-lens parallel analysis (bugs, security, architecture, performance, maintainability) with full repo context; Wave B runs a blinded 3-researcher adversarial pass on the raw diff to surface blind spots. - Persistent review reports: Findings are saved to .mz/reviews/ with date- and branch-based naming, and task state is tracked in .mz/task/<task_name>/state.md. - Use Case: Before opening a PR, run the review on your feature branch against main to get a written verdict with critical findings, missing test coverage, and adversarial blind-spot analysis. ## Quick Start Ask the assistant to review my branch against main and summarize the critical findings.

Frequently Asked Questions about review-branch

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

FAQPage Schema
How do I review all changes on my git branch before opening a PR?▼

Invoke the branch review with an optional base branch argument, defaulting to main. It dispatches a branch-reviewer agent that analyzes every changed file for bugs, architecture issues, and test coverage, then writes a report to .mz/reviews/.

What is a blinded adversarial code review pass?▼

It is a second review wave where three researchers receive only the raw diff, without repo context, to attack the change from production reliability, security, and ops perspectives. This reduces confirmation bias and surfaces blind spots the first wave missed.

Can I review a branch against a base other than main?▼

Yes, pass the base branch name as the first argument and the diff is computed against it. If the argument is empty or invalid, the skill escalates with a question rather than guessing.

When should I not use branch review?▼

Do not use it when the current branch is main or master, since there is nothing to diff, or when you want to review a GitHub pull request, which is handled by a dedicated PR review skill. Single-file reviews are better done directly.

Where are branch review reports saved?▼

Reports are written to .mz/reviews/ using the naming convention <YYYY_MM_DD>_review_branch_<branch_name>.md, with _v2, _v3 suffixes on same-day collisions. Task state is tracked separately in .mz/task/<task_name>/state.md.

Related Skills

Explore More Software Engineering Skills→
jkomorosjkomoros
9

land-branch

Rebase a feature branch onto main and merge via pull request.

Community
Intermediate
questdbquestdb
17.3k

approve-pr

Posts an existing code review as an approving GitHub PR review and adds a merge-queue label.

Official
Intermediate
facebookfacebook
247.1k

verify

Run formatting, linting, Flow type checks, and tests for React contributions.

Official
Intermediate
elaraaielaraai

east-ontology

Build a typed economic ontology graph of business resources, activities, KPIs, and decisions.

Official
Advanced