mp-review-branch

Compute branch diffs and write high-confidence review findings to REVIEW-BRANCH.md.

1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/MartinoPolo/mpx-claude-code --skill mp-review-branch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mp-review-branch
Source: https://github.com/MartinoPolo/mpx-claude-code/tree/main/_archive/skills-deprecated/mp-review-branch
Command: npx skills add https://github.com/MartinoPolo/mpx-claude-code --skill mp-review-branch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you identify issues in a feature or review branch without risking unintended changes, by producing a structured, actionable review report.

Core Features & Use Cases

  • Read-only branch scope review: Detects the current branch and automatically determines the base branch to compute the diff scope.
  • Parallel subagent evaluation: Runs specialized reviewers covering code quality, best practices, spec alignment, security, performance, and error handling.
  • Actionable reporting: Writes findings to REVIEW-BRANCH.md in a clearly ordered Critical/Important/Minor structure, and only includes high-confidence issues.

Quick Start

Ask for a branch review by telling the AI: "Review my branch and write a read-only quality report to REVIEW-BRANCH.md."

Frequently Asked Questions about mp-review-branch

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

FAQPage Schema
How do I get a read-only code review for my current git branch?

To get a read-only code review, you can request a branch quality analysis that detects your current branch, computes the diff against the base branch, and outputs findings to REVIEW-BRANCH.md without committing changes.

What does a branch diff analysis check for?

A branch diff analysis checks for scope, code quality, best practices, spec alignment, security, performance, and error handling by running specialized parallel subagents to identify actionable issues.

How do I generate a code review report without posting comments or committing changes?

You can generate a non-destructive code review report by running a read-only branch review that writes high-confidence critical, important, and minor findings directly to a REVIEW-BRANCH.md file.

Can I run a branch review if I don't know the base branch?

Yes, the branch review process includes automatic base-branch detection and disambiguation to compute the diff scope, so you do not need to manually specify the target base branch.

Does the branch review report include low-confidence issues or false positives?

No, the branch review report is constrained to only high-confidence issues to ensure the generated REVIEW-BRANCH.md file contains actionable findings without flooding it with false positives.

What is the best way to check spec alignment and security on a feature branch?

The best way to check spec alignment and security is to run a parallel subagent evaluation across the branch diff, which outputs high-confidence structural findings to a markdown report.