Skip to content
cccskills
FreePublished on GitHub

replay-regression

Independently rerun supplied proof-of-concept code against freshly built versions from before and after a change. Compare observed behavior, verify reachability through real interfaces, and preserve separate logs showing agreement, divergence, or blockers.

OriginalShow the original description

Use when independently verifying a supplied PoC against fresh live before/after deployments.

trailofbits/skills
See how to install

Good for

  • Independently check a supplied reproduction result
  • Compare behavior before and after a change
  • Verify reachability with the claimed access level
  • Record divergent results and verification blockers

Files included (1)

  • SKILL.md2.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Independently replay a PoC

When to Use

Input: candidate, frozen source records, complete sealed reproduction package and registry assignment. Use a fresh context distinct from the reproducer. Follow project guidance before target work.

When NOT to Use

Authoring or repairing the PoC. Return changes to the caller for reproduction; changed PoCs require new reproduction and replay.

Replay

  1. Read the standard and file contract. Verify the package; read setup and security guidance. Stop execution if prerequisites fail.
  2. Independently build and run actual S0/S1 only inside your attempt directory; never reuse another attempt's build output. List every build directory in build_dirs. Execute the unchanged PoC with the same input against both. Record whether S0 behaves correctly and S1 exhibits the claimed failure.
  3. Check real interface reachability using only the claimed user's/attacker's access. Save setup, versions, commands, observations and separate logs.
  4. Write and seal replay.json, referencing the reproduction record and original PoC/input. Record divergence or blockers; uncertainty stays unresolved. Release temporary resources without deleting evidence.

Report Back

Keep detailed evidence in the sealed package. Return only:

  • Status: complete or blocked, matching the record.
  • Record: sealed replay.json path, or why none was produced.
  • Result: one sentence describing observed agreement or divergence.
  • Blocker: missing prerequisite or required caller action, if blocked.

Completion means the replay attempt finished, not that the regression is confirmed.

Rationalizations to Reject

  • “The previous logs look right”: replay requires your own execution.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

address-sanitizer

FreeSummary

Build and test code with AddressSanitizer, a tool that detects invalid memory access during execution. Configure checks for C/C++ and unsafe Rust, investigate crash reports, and adjust settings for fuzzing, or testing with generated inputs.

  • Detect memory errors while fuzzing C/C++
  • Test unsafe Rust and calls to external libraries
  • Interpret an ASan crash report
trailofbits/skills7.7KUpdated Oct 22, 2026

adjudicate-regression

FreeSummary

Assess source code and live reproduction evidence to decide whether a change introduced a regression, a newly caused defect. Record supported conclusions, exclusions, severity, and unresolved gaps in an evidence-linked decision file.

  • Decide whether a change introduced a new defect
  • Separate existing bugs from newly introduced defects
  • Record missing evidence and unresolved questions
trailofbits/skills7.7KUpdated Oct 22, 2026

aflpp

FreeSummary

Sets up AFL++ to test C/C++ programs with varied generated inputs, a technique called fuzzing. Covers running tests across CPU cores, monitoring progress, reducing input collections, and reproducing crashes for investigation.

  • Running C/C++ fuzzing across multiple CPU cores
  • Exploring further after libFuzzer progress stalls
  • Monitoring fuzzing progress and stability
trailofbits/skills7.7KUpdated Oct 22, 2026

agentic-actions-auditor

FreeSummary

Audits GitHub Actions workflows that run AI coding agents. Traces how attacker-controlled content reaches prompts, checks permissions and sandbox settings, and reports evidence, severity, and fixes for prompt injection and related configuration risks.

  • Reviewing workflows that run AI coding agents
  • Tracing issue and PR content into agent prompts
  • Checking sandbox settings and user allowlists
trailofbits/skills7.7KUpdated Oct 22, 2026

algorand-vulnerability-scanner

FreeSummary

Reviews Algorand smart contracts written in TEAL or PyTeal for 11 vulnerability patterns. Produces a complete coverage table and findings with code references, severity ratings, and suggested fixes, with optional automated checks using Tealer.

  • Security checks before an Algorand contract audit
  • Reviewing TEAL or PyTeal transaction validation
  • Verifying fixes for reported vulnerabilities
trailofbits/skills7.7KUpdated Oct 22, 2026

atheris

FreeSummary

Set up Atheris to test Python code and C extensions with automatically varied inputs. It guides test harness creation, coverage tracking to explore more code, and AddressSanitizer setup for finding memory errors.

  • Fuzzing a Python package or parser
  • Investigating memory corruption in Python C extensions
  • Turning raw bytes into typed test arguments
trailofbits/skills7.7KUpdated Oct 22, 2026

See all skills by trailofbits

Report a problem with this skill