patch-critique

Score candidate patches against a rubric using test outcomes and diff analysis.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/paulingham/.claude --skill patch-critique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: patch-critique
Source: https://github.com/paulingham/.claude/tree/main/skills/patch-critique
Command: npx skills add https://github.com/paulingham/.claude --skill patch-critique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluates candidate patches at the Final Gate by analyzing test results and the patch diff to decide PATCH_APPROVED or PATCH_REJECTED.

Core Features & Use Cases

  • Spawns the patch-critic agent — Sonnet executor + Opus advisor — to score the patch against four dimensions.
  • Performs multi-dimensional rubric-based judgments to support decision-making in automated pipelines.
  • Integrates inputs from test results, candidate diff, intake spec, and verification evidence to drive gating decisions.

Quick Start

Provide the candidate patch diff and the latest test results to the patch-critic and run the Final Gate evaluation.

Frequently Asked Questions about patch-critique

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

FAQPage Schema
How do I automate code review for patch diffs and test results?

Automating code review for patch diffs involves scoring candidate patches at the Final Gate by analyzing test outcomes and diffs to decide PATCH_APPROVED or PATCH_REJECTED. It uses a patch-critic agent pairing to provide multi-dimensional rubric judgments for automated pipelines.

What is a Final Gate evaluation in automated patch pipelines?

A Final Gate evaluation is a decision point that scores candidate patches by analyzing test outcomes and the patch diff to output PATCH_APPROVED or PATCH_REJECTED. It operates with a Sonnet executor and Opus advisor agent pairing to provide multi-dimensional rubric judgments.

How do I evaluate code changes using a multi-dimensional rubric?

Evaluating code changes using a multi-dimensional rubric requires spawning a patch-critic agent to score the patch against four dimensions. It integrates test results, candidate diff, intake spec, and verification evidence to drive gating decisions in automated pipelines.

Can I use this patch critic agent with Sonnet executor and Opus advisor?

Yes, this Skill operates with a patch-critic agent pairing that uses a Sonnet executor and Opus advisor. This pairing scores candidate patches against four dimensions by analyzing test outcomes and patch diffs to support decision-making in automated pipelines.

What inputs do I need to provide to score candidate patches?

To score candidate patches, you need to provide the candidate patch diff and the latest test results to the patch-critic. The evaluation also requires access to the intake task description and verification evidence to drive gating decisions.

When should I not use automated patch gating for code changes?

Automated patch gating is not suitable when you lack the required inputs, such as candidate diffs, latest test results, intake task descriptions, or verification evidence. The patch-critic requires all these data sources to perform its multi-dimensional rubric judgment effectively.