issta-reproducibility
Use when strengthening ISSTA reproducibility and verifiability evidence, covering pinned subject programs and benchmark versions, random seeds and timeout budgets, non-determinism disclosure for fuzzing and analysis, claim-to-evidence traceability, tool availability statements, and keeping the artifact consistent with the paper's tables.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill issta-reproducibility --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# ISSTA Reproducibility Use this before submission and again before the artifact deadline. Verifiability and transparency are named ISSTA evaluation criteria, so reproducibility is scored, not optional. Reopen the current call and artifact instructions to confirm what the cycle requires. ## Evidence map - Map each empirical claim — a detection rate, a coverage gain, a bug count, a speedup — to a verifiable location: a table, the artifact, or a logged run that a reader could regenerate. - Pin the substrate: benchmark version (e.g. the Defects4J revision), subject-program commit SHAs, the extraction date of any mined corpus, and the exact toolchain versions. "The latest version" is not reproducible. - Fix and report the stochastic knobs: random seeds, timeout budgets, iteration or generation counts, and hardware, because a fuzzing or search result at one budget says little about another. - Disclose non-determinism honestly. Where results vary between runs, report the run count and the observed spread rather than a single golden run, and say which tables are means over runs. - Give an availability statement: what is released, under what license, and where, or an honest reason for with
- Evidence map
- Claim-to-evidence audit table
- Vignette: a fuzzing evaluation
- Degrees of reproducibility
- Output format
What does the issta-reproducibility skill do?
Use when strengthening ISSTA reproducibility and verifiability evidence, covering pinned subject programs and benchmark versions, random seeds and timeout budgets, non-determinism disclosure for fuzzing and analysis, claim-to-evidence traceability, tool availability statements, and keeping the artifact consistent with the paper's tables.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill issta-reproducibility --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 984 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.