Independently reproduce a reported runtime or compiler bug in a local repository. Build the baseline, exercise the actual artifact or compiler, and save logs and structured records distinguishing reproduction, absence of the behavior, and setup blockers.
Use when a named runtime or compiler bug in a local repository needs independent reproduction.
Review the instructions the agent will receive before you install.
Use for the reproduction step of patching-bugs with one finding.json and a local
baseline checkout. Read the record contract.
Before target commands, follow its project guidance.
Do not use for bug discovery, patching, or a claim that cannot be exercised locally. Report a blocker when the build or environment cannot exercise the claim.
Select failure_type from the record contract. Build the current baseline with the
project's own command. Exercise the planned scoped inputs before any edit and
retain their observations, including valid controls. Save raw stdout, stderr,
exit status, and timing. If the behavior is absent with trustworthy evidence,
report not_reproduced; if setup or observations are unreliable, report blocked.
Runtime: exercise the built target_artifact with a PoC that records PATCH_LOADED
as defined in the contract, then prints PATCH_REACHED immediately before the assertion.
Exit nonzero for the bug, zero otherwise; a setup crash is inconclusive.
Compile: record the target expected_diagnostic from the failed compiler invocation;
use empty poc_argv and null target_artifact.
Save any unchanged PoC source under reproduce/poc/ and raw receipts
under reproduce/receipts/. Write reproduce.json with the baseline commit,
command argument arrays, artifact path, observed result, outcome, and your agent
identity. Set finding.status to reproduced or not_reproduced from the result.
If reproduction is blocked, leave finding.status as hypothesis.
{
"schema_version": 1,
"failure_type": "runtime",
"outcome": "reproduced",
"baseline_commit": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
"build_argv": ["python", "build.py"],
"poc_argv": ["python", "poc.py"],
"target_artifact": "dist/app.py",
"observed": "The PoC wrote outside uploads after PATCH_REACHED.",
"blocker": null,
"agent": "reproducer-1"
}
reproduce/ directory, including the PoC and record, using
the record helper: run
uv run --no-project <script> manifest <reproduce-step-dir>. Then check the
record before handoff. State blocked with the actual failure when build or setup
prevents a valid run.| Shortcut | Required action |
|---|---|
| A unit test imitates the bug. | Exercise the target compiler or built runtime artifact. |
| A nonzero exit proves reproduction. | Require the target diagnostic, or runtime marker and assertion. |
No reviews yet. Tell others what you thought.
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.
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.
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.
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.
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.
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.
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.