pr-review

Reviews git diffs and reports bugs, regressions, missing tests, and style issues per file.

Updated Mar 31, 2026

Search Tags:#code review #pull request #test coverage #risk assessment #regression detection #git diff #mobile-friendly

Ready to run

npx skills add https://github.com/dimakis/mitzo --skill pr-review-dimakis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/dimakis/mitzo/tree/main/skills/pr-review
Command: npx skills add https://github.com/dimakis/mitzo --skill pr-review-dimakis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly review a code diff and spot bugs, regressions, missing tests, unsafe assumptions, and unclear changes before you make edits.

Core Features & Use Cases

Diff-first review using git diff or branch comparisons to focus the feedback on what actually changed.
Structured risk checklist per file covering bugs, regressions, missing tests, unsafe assumptions, and style/clarity.
Mobile-friendly output formatted as a compact, grouped list that’s easy to read on a phone screen.

Quick Start

Ask for a review by saying: "Review the current diff for my branch and summarize the findings by file, including bugs, regressions, missing tests, and unsafe assumptions."

Frequently Asked Questions about pr-review

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

FAQPage Schema

How do I review a git diff for bugs and regressions before merging?▼

To review a git diff for bugs and regressions, run the appropriate git diff commands to compare branches or working tree changes. The review groups findings per file, identifying bugs, regressions, missing tests, and unsafe assumptions in a compact format.

What is a pull request risk assessment and how does it work with code diffs?▼

A pull request risk assessment analyzes the specific code diff to spot unsafe assumptions and potential regressions. It applies a structured risk checklist to changed files, ensuring feedback focuses strictly on what actually changed before merging.

Can I check test coverage and style issues from a branch comparison?▼

Yes, you can check test coverage and style issues from a branch comparison. The review process evaluates changed files for missing tests and style or clarity issues, outputting a compact, grouped list that is easy to read on mobile devices.

What's the best way to get mobile-readable code review feedback?▼

The best way to get mobile-readable code review feedback is to run a diff-first review that formats findings as a compact, grouped list per file. This format ensures bugs, regressions, and missing tests are easy to read on a phone screen.

Does the code review process modify my working tree files automatically?▼

No, the code review process does not modify your working tree files automatically. It strictly produces a read-only grouped per-file review of bugs and style issues until you explicitly request edits.