Skip to content
SkillModel-led1,062 tokens in use

prove-patch

The prover stage of patching-bugs: run scoped cases on baseline and patched trees, then confirm the bug returns when the patch is reverted.

8,319 stars on the repository CC-BY-SA-4.0trailofbits/skills · plugins/patching-bugs/skills/prove-patch
/plugin marketplace add trailofbits/skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing prove-patch costs

19tokens idle
1,062tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

shelldetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure12/25
  • Examples6/15
  • Output15/15
  • Size10/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance52
  • Community64
  • Maturity32
  • Momentum40

Prove-patch gives an independent agent the baseline commit, the final patch commit and the declared repair scope. It reviews the planned cases and the patch without the patcher’s conclusion, runs every case on clean baseline and patched trees with one harness, and keeps raw output as receipts.

It then runs the project’s relevant checks and a three-arm helper: the baseline must fail, the patch must pass, and a full revert must fail again. The result is a prove record with a manifest, listing findings, evidence gaps and unproven limits.

What You Get

  • A prove.json record covering every planned case by unique check id
  • Raw stdout, stderr, exit status, timing, command and harness source for each baseline and patched run
  • A three-arm result with source receipts that pin the commits and show the reverted tree equals the baseline tree
  • A list of findings, evidence gaps and specific unproven limits to return to the orchestrator

Common Use Cases

  • Independently checking a patch written by another agent
  • Confirming that a fix covers a bounded class of inputs and keeps valid behavior
  • Deciding whether a failed attempt needs a new patch round

What Makes It Unique

The prover must be a different agent from the patcher, may not edit the patch, and refuses to validate an uncommitted tree. It needs at least two distinct failing representatives and a valid control for a bounded class, and an empty list of unproven limits leaves the result inconclusive.

Under The Hood

The agent reads a record contract and runs bundled Python scripts through uv: a three-arm helper that builds the pinned baseline, patched and reverted trees in temporary Git worktrees, a native proof assessor, and a record validator that writes manifests. It runs the project’s build and test commands and a retained harness, and writes receipts and records into the run directory. It does not edit the patch and makes no network calls of its own.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers