reproduce-regression is the reproduction stage of the regression-hunt plugin from Trail of Bits. Given sealed preparation and discovery packages plus one candidate, it builds the real before (S0) and after (S1) systems with their services and traces the candidate to a real user or attacker entry point.
It then writes one portable proof of concept, runs it against both live deployments with identical input, and records whether S0 behaves correctly and S1 shows the claimed failure. Mocks, extracted functions and simulated systems are not accepted.
What You Get
- A sealed reproduce.json with observations and false-positive checks
- A portable PoC and the exact input used against both deployments
- Saved setup, tool and dependency versions, sanitized configuration and separate logs for each system
- A status of complete or blocked, with the missing prerequisites listed when blocked
Common Use Cases
- Proving that a suspected regression in a pull request changes behavior in the running product
- Checking that a build or install finding shows up in the supported build workflow
- Recording a blocked attempt with its exact prerequisites so a person can finish it
What Makes It Unique
The skill demands a live-system experiment. It says that a unit test, mock or extracted function cannot establish a regression, and it ties each finding to a real entry point. It also separates finishing the experiment from confirming the regression: completion only means the run ended. Independent verification of an existing PoC belongs to the replay skill.
Under The Hood
The skill is a short instruction file with no scripts of its own. It tells the agent to read the plugin’s standard and file contract, then build, install and run the actual before and after systems with their services, which means running shell commands, building software and starting deployments on the machine. The agent writes the PoC, logs, configuration copies and the reproduce.json record to files inside its own attempt directory, lists every build directory, and releases temporary resources at the end while keeping the evidence. It does not fetch web pages or call APIs by its own instruction, though a build may download dependencies.