replay-regression is the verification stage of the regression-hunt plugin from Trail of Bits. It takes a candidate, its frozen source records and a sealed reproduction package, then runs the same unchanged PoC in a fresh context against its own builds of the before (S0) and after (S1) systems.
The skill records whether S0 behaves correctly and S1 shows the claimed failure, checks that the interface is reachable with only the claimed user’s access, and writes a sealed replay.json. Completion means the replay finished, not that the regression is confirmed.
What You Get
- A sealed replay.json that references the reproduction record and the original PoC and input
- Separate logs, versions, commands and observations for the S0 and S1 runs
- A list of every build directory used, kept apart from other attempts
- A short report back: status, record path, one-sentence result and any blocker
Common Use Cases
- Confirming that a regression PoC written by another agent works on a clean build
- Checking that a claimed vulnerability is reachable through a real interface with the attacker’s own access
- Recording a divergence between the reproducer’s logs and a second run before a report is written
What Makes It Unique
Replay is separated from reproduction on purpose. The replayer may not repair the PoC; a changed PoC goes back for new reproduction and replay. The skill also rejects trusting earlier logs and requires its own execution, which is a stricter check than most verification prompts ask for.
Under The Hood
The skill is a short prose checklist with no scripts of its own. It tells the agent to read the regression standard and evidence file contract in the plugin, then build and run the target systems, execute the PoC, save logs and write and seal a JSON record. That means running build and deploy commands and writing files inside an attempt directory, and it may start services the target needs.