mp-review-changes

Reviews uncommitted working-tree and staged diffs, generating a structured report with critical, important, and minor findings.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns your local uncommitted diff into a structured, high-signal code review report without making any source changes.

Core Features & Use Cases

  • Read-only change inspection: Scans both working-tree and cached diffs to define an explicit review scope.
  • Parallel review perspectives: Produces findings from code quality, best practices, and spec alignment subagents.
  • Actionable reporting: Writes issues into a single REVIEW-CHANGES.md report with clear severity sections when issues are found.

Quick Start

Run the mp-review-changes skill to generate a read-only review report for your current uncommitted changes.

Frequently Asked Questions about mp-review-changes

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

FAQPage Schema
How do I review uncommitted changes before committing?

Review uncommitted changes by collecting scoped working-tree and staged git diffs, then generating structured findings from multiple perspectives like code quality and spec alignment. This process provides fast feedback before you commit or open a PR.

Can I get a code review without modifying my source files?

Yes, you can perform a read-only code review that scans your uncommitted diff without making any source changes. It only writes a REVIEW-CHANGES.md report when issues are found, ensuring your working tree remains untouched.

How do I check if my working tree diff aligns with project specifications?

Check spec alignment by applying a parallel review perspective to your uncommitted diff. This evaluates your working-tree changes against project specifications and generates actionable findings within a structured review report.

What's the best way to find issues in staged git changes?

The best way is to scan both cached and working-tree diffs to define an explicit review scope. This identifies code quality and best practice issues, categorizing them by severity with concrete fixes in a single report.

Does this local review process work for both staged and unstaged files?

Yes, the review process works for both staged and unstaged files. It collects scoped diffs from both the working tree and cached changes, applying parallel review perspectives to generate a comprehensive feedback report.

When should I not use an automated diff review for my developer workflow?

You should not use this read-only diff review when there are no uncommitted changes to inspect, as it relies on scoped working-tree and staged diffs. It is designed specifically for pre-commit feedback rather than post-merge analysis.