cav-reproducibility

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-reproducibility --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

# CAV Reproducibility Use this before submission and again before camera-ready. In computer-aided verification, reproducibility is not a courtesy — a benchmark result is only meaningful relative to a **fixed benchmark set, pinned tool versions, and a stated resource budget**, and a soundness claim is only credible if it ships a **checkable witness**. The goal is that a competent reader could rerun your evaluation and re-check your correctness claims and reach your conclusions. ## Evidence map - Map each theorem, technique claim, and reported benchmark number to a **verifiable location** — a proof (body or appendix), a script in the artifact, or a table regenerated from logged runs. - For techniques, give enough of the algorithm, parameters, and encoding that a reader could re-implement or rerun it. - For benchmark evaluations, report the exact **benchmark set and revision**, the **baseline tools and versions**, the **resource limits** (per-instance time and memory), the **hardware and core count**, and the **number of runs**. - For soundness claims, emit a **certificate/witness** (unsat proof, DRAT, an SV-COMP-style witness, an Isabelle/Coq script) and an independent checker — a ba