icse-reproducibility
Use when building the verifiability story of an ICSE research-track paper, covering the open-science policy's sharing-by-default expectation, the Data Availability section, anonymized replication packages at review time, provenance pinning for mining and LLM studies, and honest non-sharing justifications.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-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.
# ICSE Reproducibility At ICSE, reproducibility is not an optional badge chase bolted on after acceptance — it is one of the four scored review criteria. The 2027 call (read 2026-07-08) scores **Verifiability and Transparency**: whether the paper gives enough information to understand how the innovation works, how data was obtained, analyzed, and interpreted, and whether independent verification or replication is supported. Build for that score at review time; the post-acceptance badge process (`icse-artifact-evaluation`) then becomes cheap. ## The open-science posture The research track is governed by the ICSE Open Science policy. Its verified 2027 shape: - Research results should be accessible to the public; empirical studies should be reproducible where possible. - **Sharing is the default; non-sharing is what requires justification.** - Authors provide anonymized links to data/repositories, or upload anonymized material via HotCRP's supplementary option. - Authors who cannot share add a short statement of reasons in a **Data Availability section placed after the Conclusion**. - Sharing is not formally mandatory for acceptance — but it is scored terrain. ## Availability statemen
- The open-science posture
- Availability statements that read as honest
- Reproducibility evidence by study type
- Determinism ledger for tool experiments
- Anonymity vs verifiability at review time
- Five-question self-audit
- Reverify each cycle
- Output format
What does the icse-reproducibility skill do?
Use when building the verifiability story of an ICSE research-track paper, covering the open-science policy's sharing-by-default expectation, the Data Availability section, anonymized replication packages at review time, provenance pinning for mining and LLM studies, and honest non-sharing justifications.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-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 909 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.