Patching-bugs coordinates the full repair of one named bug in a local Git repository. It normalizes the report into a finding record, then hands each stage to a fresh agent: reproduction, independent validation, up to three patch attempts, independent proof, and a regression hunt over the patch range.
Every handoff is a validated JSON record with a hash manifest, and results are transcribed from receipts. The run ends with an auditor report and, only when the patch is verified, a maintainer report. It never pushes or opens a pull request.
What You Get
- A run directory outside the target tree holding the finding, reproduction, validation, patch, proof and regression records
- One local patch commit with fix.patch and tests.patch for each attempt
- A report.html for the auditor on every run, including failed and inconclusive ones
- A maintainer-report.html only when the validated records establish a verified patch
- A verdict such as ready, ready with concerns, not ready or inconclusive, derived from receipts
Common Use Cases
- Fixing a security bug an auditor reported against a local codebase
- Checking a compile failure or runtime crash against its stated invariant before changing code
- Producing reviewable proof that a patch fixes the bug and breaks nothing nearby
What Makes It Unique
Different fresh agents do reproduction, validation, patching and proof, and the validator never sees the reproducer’s transcript. A runtime reproduction counts only when the exact PATCH_REACHED marker appears. The skill lists shortcuts to reject, such as trusting the patcher’s own test run or treating a missing receipt as close enough.
Under The Hood
The agent reads SKILL.md, a record contract and JSON schemas in the plugin, and runs bundled Python scripts through uv to validate records, write manifests, run a three-arm proof and render reports. It runs the project’s own build and test commands, uses Git to read baseline objects, create worktrees and make one local commit, dispatches other agents, and writes many files into a run directory. It does not push or open pull requests, and the supplied bug report is treated as data.