Hunt-regressions takes a sealed preparation, the frozen before and after sources, change context and a registry assignment, and looks for defects the change may have introduced. It reads commit messages, PR discussion and security documentation for intent and supported use.
The agent reviews the whole diff, traces changed behavior through callers to real interfaces, and records each lead with its changed code, previously supported behavior, trigger, proposed defect, false-positive checks and the proof needed. It cannot confirm findings, and an empty list is valid.
What You Get
- Candidate files that each describe one lead and what proof it needs
- A sealed hunt.json with IDs, file mappings, coverage and limitations
- Leads that suggest old bugs or incomplete fixes kept for adjudication
- A short report back with status, record path, candidate count and coverage gaps
Common Use Cases
- Reviewing a pull request for behavior it may have broken
- Tracing a refactor through its callers to supported interfaces
- Recording partial coverage when a prerequisite blocks the review
What Makes It Unique
The hunter stays blind to later fixes and other reviews and must show a supported interface that reaches a suspect helper. Leads are reserved by a stable hypothesis key, so a retry reuses the same candidate IDs, and building the PoC is left to a separate reproduction stage.
Under The Hood
The agent reads SKILL.md, a regression definition and an evidence file contract, verifies the sealed preparation, and reads the frozen sources. It runs a bundled Python registry script from the plugin to reserve candidate IDs and writes candidate files and a sealed JSON record into the campaign directory. It does not build or run target code in this stage.