hpca-reproducibility
Use when strengthening HPCA reproducibility: pinning the result chain from simulator commit through config, workload, sampled region, and statistics, building one manifest per figure, recording machine state for silicon runs, and keeping the environment resurrectable for the IEEE artifact-badging round.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-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.
# HPCA Reproducibility Use this to make an HPCA paper's results reconstructable — by a reviewer during the window, by an artifact evaluator after acceptance, and by you six months later when the environment has drifted. HPCA's artifact badges are **IEEE reproducibility badges** earned on a separate AE HotCRP, so build toward that pipeline, not the ACM one. ## Pin the result chain Every figure in the paper should trace back through an unbroken chain: ```text simulator commit (or machine + firmware) -> configuration file (core, cache, DRAM, interconnect) -> workload + input + sampled region -> raw output logs -> statistics script -> the figure/table in the PDF ``` If any link is unpinned — a simulator built from "latest," a config edited by hand, a region chosen ad hoc — the result is not reproducible, only re-runnable by you. ## One manifest per figure Give each headline figure a manifest that names its commit, config, workload, region, seed/trial count, and the exact command that regenerates it. A `regen.sh` per figure that reproduces the artifact from raw logs turns "trust me" into "run this." | Chain link | What to pin | Failure if unpinned | |---|---|---| | Simulator | Commit ha
- Pin the result chain
- One manifest per figure
- Record machine state for silicon
- Handle non-redistributable workloads
- Keep the environment resurrectable
- Reproducibility checklist
What does the hpca-reproducibility skill do?
Use when strengthening HPCA reproducibility: pinning the result chain from simulator commit through config, workload, sampled region, and statistics, building one manifest per figure, recording machine state for silicon runs, and keeping the environment resurrectable for the IEEE artifact-badging round.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-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.