Regression-hunt runs a campaign that investigates regressions in pull requests of any status or in commits, including local ones. The coordinator saves the change list, sets up a campaign directory outside the plugin, saves root guidance files from each target commit, and reserves each stage’s assignment through a registry script.
It then dispatches a fresh agent for each stage, checks and accepts each sealed record before updating the index and ledger, retries blocked work, and requests reports on confirmed findings, unresolved work and coverage gaps. Saved progress can be resumed.
What You Get
- A campaign directory with scope.json, campaign.json, progress.md, a registry and a ledger
- Revision-specific copies of root guidance files saved by change and target SHA
- Sealed records from each stage, accepted by the registry before the index is updated
- Reports covering confirmed findings, unresolved work and coverage gaps
- A resume path that re-checks accepted records and reuses unchanged evidence
Common Use Cases
- Running a regression review over a set of merged pull requests
- Investigating commits in a local repository for introduced defects
- Resuming a saved campaign after an interruption
What Makes It Unique
Confirmation needs separate reproduction, replay and adjudication agents, and dispatch, process exit or a completion message never counts as proof that work finished. The coordinator rejects the view that nothing reproduced means a clean review, and installation grants no permission for cloud spending, source export, publication or patching.
Under The Hood
The agent reads SKILL.md, a regression definition and an evidence file contract, and runs a bundled Python registry script to initialize the campaign, assign work, accept records, check them and retry stages. It fetches remote guidance files by SHA, reads local ones from Git objects, spawns fresh agents with full file contents in their prompts, and writes records, a ledger and progress notes into the campaign directory. It checks that stopped agents are terminated before a retry.