isca-review-process
Use when reasoning about how an ISCA submission is evaluated — the two-round review structure with December and February reviewer waves, what the combined rebuttal-and-revision window means for decisions, PC-meeting dynamics at a flagship architecture venue, and how to read the eventual outcome.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-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.
# ISCA Review Process Knowing the pipeline changes author behavior at three points: how the paper is written (for two waves of readers), how the February window is used (it permits revision, not just argument), and how the decision is interpreted. The stage structure below is the verified ISCA 2026 calendar; internal committee mechanics are described as community-typical practice, labeled as such, because programs rarely publish them. ## The 2026 pipeline as verified | Stage | 2026 dates | Author-visible? | |---|---|---| | Abstract registration | Nov 10, 2025 | yes — HotCRP | | Paper submission | Nov 17, 2025 | yes | | Round 1 reviews written | due Dec 19, 2025 | no (delivered later) | | Round 2 reviews written | due Feb 13, 2026 | no | | Rebuttal + revision window | Feb 16 - Mar 6, 2026 | yes — the pack's pivot point | | PC deliberation and decisions | after the window; exact 2026 date 待核实 | outcome only | | Conference | Jun 27 - Jul 1, 2026, Raleigh | yes | ## What two rounds imply A two-round structure typically means an early wave of reviews on every paper, after which papers that remain viable receive additional expert reviews in the second round. Two operational consequences
- The 2026 pipeline as verified
- What two rounds imply
- The combined rebuttal/revision window
- Inside the committee room (typical practice, not CFP text)
- Reading the outcome
- Confidentiality and conduct
- Author-side calendar hooks
What does the isca-review-process skill do?
Use when reasoning about how an ISCA submission is evaluated — the two-round review structure with December and February reviewer waves, what the combined rebuttal-and-revision window means for decisions, PC-meeting dynamics at a flagship architecture venue, and how to read the eventual outcome.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill isca-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.