Bug Reproducer

Turn a codebase or bug report into evidence. When no bug is supplied, discover concrete candidates from the code and its contracts, then try to prove the strongest candidates with focused tests. Never present a suspicion as a confirmed bug.

Enforce two approval gates

Treat invocation of $bug-reproducer as consent to inspect only. Even when the user says find and fix, apply, or do it, do not interpret the initial request as approval for unseen changes.

Before either approval, do not create or edit project files, install dependencies, run formatters or migrations, modify configuration, generate reports, create worktrees, or execute commands likely to mutate project state. Read source, configuration, documentation, existing tests, user-supplied logs, and Git history. Run an existing targeted test only when it is clearly safe and does not require project changes.

Gate 1 — test the candidate

After read-only discovery or report inspection, present and stop at:

## Bug candidates