pre-pr-review

Review git diffs and block merges until blocking issues are resolved.

Updated Apr 27, 2026

Search Tags:#isolation #quality-assurance #code-review #pull-request #diff-analysis #pre-pr-review

Ready to run

npx skills add https://github.com/MichielDean/LLMem --skill pre-pr-review-michieldean

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adversarial pre-PR review enables isolation-aware code critique to surface defects, ensure code quality, and enforce standards before a pull request is created.

Core Features & Use Cases

Isolated reviewer subagent: reviews diffs without author context to prevent bias.
Diff + originals comparison: compare modified, original, and diff content to detect regressions.
Structured output & gating: outputs issues with severity levels and blocks PR until Blocking/Required issues are addressed.
Regression & quality checks: identifies behavioral changes, missing context, and potential security concerns.

Quick Start

Invoke the pre-pr-review workflow before creating a PR to have an isolated reviewer assess the diff and block the merge until issues are resolved.

Frequently Asked Questions about pre-pr-review

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

FAQPage Schema

How do I perform an adversarial code review before creating a pull request?▼

Adversarial pre-PR review analyzes the diff between your main branch and HEAD to detect defects, behavioral changes, and regressions. It uses an isolated reviewer subagent to prevent author bias and outputs a deterministic report blocking merges until issues are resolved.

What does isolated reviewer subagent mean for pull request quality assurance?▼

An isolated reviewer subagent performs code review without author context to prevent bias. It evaluates the diff independently to surface defects, enforce quality gates, and block the pull request until all blocking and required issues are addressed.

Can I use automated diff analysis to block pull requests with regressions?▼

Yes, automated diff analysis blocks pull requests by enforcing quality gates before merging. It compares original and modified files to detect regressions and behavioral changes, preventing the merge until all blocking and required issues are resolved.

How does diff comparison between main and HEAD detect behavioral changes?▼

Diff comparison between main and HEAD detects behavioral changes by analyzing modified content against original files. This pre-PR review surfaces regressions and missing context, outputting a structured report that blocks merges until issues are fixed.

When do I need pre-PR gating for code quality assurance?▼

Pre-PR gating is needed when you must enforce quality standards and block merges before creating a pull request. It performs adversarial code review to detect defects and regressions, ensuring blocking and required issues are resolved before merging.