hpca-review-process
Use when reasoning about the HPCA review pipeline: the double-blind process, what a single combined rebuttal/revision window means, champion dynamics at the program-committee meeting, how to read each outcome, and how confidentiality and the preprint policy shape expectations.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-review-process --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 Review Process Use this to set expectations about how HPCA reviews a paper and decides its fate. Understanding the pipeline turns anxiety into a plan: you can predict what the rebuttal/revision window is for and what each outcome signals. ## The pipeline HPCA runs a **double-blind** review. After the late-July gate, papers are assigned to program-committee reviewers, reviews are written through the autumn, and — in recent cycles — authors get a **single combined rebuttal/revision window**: one period in which you both respond to reviews and may revise the paper, rather than two separate review rounds. Decisions follow a program-committee meeting; HPCA 2027's reported notification is November 6, 2026 (待核实 the exact rebuttal window). ## What the single window means Unlike venues with two review rounds, HPCA's combined window compresses "argue" and "change the paper" into one effort. Plan for both at once: - Reviewers see your response *and* a revised paper, so a claim you defend in prose should also be reflected in the revision. - The window is short; the objection ledger and staging shelf (see `hpca-author-response` and `hpca-supplementary`) must be ready before it opens. ##
- The pipeline
- What the single window means
- Champion dynamics at the PC meeting
- Read reviews for the deciding objection
- Confidentiality and preprints
- Expectation-setting pass
- Output format
What does the hpca-review-process skill do?
Use when reasoning about the HPCA review pipeline: the double-blind process, what a single combined rebuttal/revision window means, champion dynamics at the program-committee meeting, how to read each outcome, and how confidentiality and the preprint policy shape expectations.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill hpca-review-process --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.