pr-review-enforcer

name	pr-review-enforcer
description	Review diffs like a senior engineer by checking correctness, architectural fit, style, missing tests, security smells, and migration or operational risk. Use when asked to review a pull request, patch, staged changes, or proposed code edits.

Pr Review Enforcer

Overview

Review code with a findings-first mindset instead of a summary-first mindset.

Core Workflow

1. Read the diff and the surrounding code before judging the change.
2. Look for correctness issues first: regressions, edge cases, state handling, concurrency, data integrity, and compatibility.
3. Check architecture and maintainability: layering, ownership boundaries, duplication, naming, and hidden complexity.
4. Check safety gaps: missing tests, weak observability, migrations, rollout risk, secrets, and authorization concerns.
5. Report findings in priority order with file references and concise reasoning.

Deliver

• Lead with actionable findings, ordered by severity.
• Include open questions only after concrete issues.
• Mention testing gaps and residual risk even when the diff looks sound.
• State explicitly when no findings are discovered.

Guardrails

• Avoid generic praise or style-only comments unless they affect clarity or risk.
• Do not review from the diff alone when nearby code changes the meaning.
• Keep comments specific enough that the author can act on them quickly.