Skip to content
Security
Skill

/reproduce-regression

Use when deploying before/after systems and building a live-system PoC for a regression candidate.

GuideBOOST
From plugin
trailofbits-skills
7.7k95 skills30 agents8 commands1 MCP
Install
$ npx -y skills add trailofbits/skills --skill reproduce-regression --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/reproduce-regression

Context preview

The summary Claude sees to decide when to auto-load this skill.

Use when deploying before/after systems and building a live-system PoC for a regression candidate.

SKILL.md

reproduce-regression.SKILL.md
name: reproduce-regression
description: Use when deploying before/after systems and building a live-system PoC for a regression candidate.

Reproduce a candidate

When to Use

Input: sealed preparation/discovery packages, candidate and registry assignment. Follow [project guidance](../../references/evidence.md#project-guidance) before target work.

When NOT to Use

Independent verification of an existing PoC; use replay.

Reproduce

1. Read the [standard](../../docs/regression-definition.md) and [file contract](../../references/evidence.md). Verify inputs; read security guidance. Stop execution if prerequisites fail. 2. Build and run actual S0/S1 with required services. Trace the candidate to a real user/attacker entry point. Build/install CLIs and libraries; exercise supported interfaces. For build findings, execute the supported build workflow. 3. Create and execute a portable PoC against both live deployments with identical input and comparable configuration. Record whether S0 behaves correctly and S1 exhibits the claimed failure. No mocks, extracted functions or simulated systems. 4. Save setup, tool/dependency versions, sanitized configuration, input, PoC, revisions, commands and separate logs. Record observations and false-positive checks in `reproduce.json`. If blocked, retain attempted setup and exact prerequisites. Build and deploy only inside your attempt directory, and list every build directory in `build_dirs`. 5. Release temporary resources without deleting evidence. Record their disposition, then seal the package.

Report Back

Keep detailed evidence in the sealed package. Return only:

  • Status: `complete` or `blocked`, matching the record.
  • Record: sealed `reproduce.json` path, or why none was produced.
  • Result: one sentence describing observed S0/S1 behavior.
  • Blocker: missing prerequisite or required caller action, if blocked.

Completion means the experiment finished, not that the regression is confirmed.

Rationalizations to Reject

  • “The unit test proves it”: synthetic tests cannot establish a regression.
Read more
Ships withtrailofbits-skills

A Claude Code plugin marketplace from Trail of Bits providing skills to enhance AI-assisted security analysis, testing, and development workflows. Codex can load this marketplace through its Claude marketplace compatibility.

Get the whole plugin

Other skills on trailofbits-skills.