pr-review-harness

Enforce deterministic checks and multi-agent review before merging code changes.

Updated Feb 13, 2026
One-click install
npx skills add https://github.com/mwathiben/PropManager --skill pr-review-harness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-harness
Source: https://github.com/mwathiben/PropManager/tree/main/.claude/skills/pr-review-harness
Command: npx skills add https://github.com/mwathiben/PropManager --skill pr-review-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The gate to merge substantive changes is tests green AND review addressed — never CI alone. The harness coordinates mandatory deterministic checks and a parallel review panel to ensure code quality and policy compliance before merge.

Core Features & Use Cases

  • Deterministic checks: run lint, tests, and static analysis on changed paths.
  • Review panel: spawn in parallel multiple agents to surface findings and validate changes.
  • Triage & fix workflow: guide triage, require fixes, and re-run checks before merging.
  • Merge gating: enforce a formal merge process that ensures readiness and reduces regressions.

Quick Start

Run the PR review harness on the diff to verify tests, lint, and panel reviews before merging.

Frequently Asked Questions about pr-review-harness

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

FAQPage Schema
How do I automate code review and enforce merge gating for substantive pull requests?

Automated merge gating enforces deterministic checks and a multi-agent review panel before allowing merges. The harness coordinates lint, tests, and static analysis on changed paths, then spawns parallel review agents to surface findings and validate changes.

What is a multi-agent review panel for PR quality assurance?

A multi-agent review panel spawns multiple agents in parallel to surface findings and validate changes. This review panel operates alongside deterministic checks to ensure code quality and policy compliance before merge.

How do I run lint, tests, and static analysis only on changed paths in a pull request?

Deterministic checks run lint, tests, and static analysis on changed paths. The harness applies these automated checks specifically to changes touching app, database, routes, or resources/js directories.

Can I use automated PR checks for changes touching app, database, routes, or resources/js directories?

Automated PR checks apply directly to changes touching app, database, routes, or resources/js directories. The harness coordinates deterministic checks and review triage specifically for these substantive changes before merge.

What's the best way to triage and fix code review findings before merging?

A triage and fix workflow guides triage, requires fixes, and re-runs checks before merging. This process follows deterministic checks and the review panel stage to ensure all findings are addressed.

When should I not use automated merge gating for pull requests?

Automated merge gating targets substantive changes touching app, database, routes, or resources/js directories. Trivial changes outside these paths may not require the full deterministic checks and multi-agent review panel workflow.