micro-review-process
Use when reasoning about how a MICRO submission is judged — the double-blind HotCRP pipeline from the April deadline through the June rebuttal/revision window to the early-July notification, what reviewers score in a microarchitecture paper, the professional-conduct rules, and how the new Industry Track review differs.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-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.
# MICRO Review Process Model of the pipeline a MICRO submission enters, anchored to the 2026 (59th) cycle as verified 2026-07-08. Committee composition and internal mechanics vary by year and are only partly public — items marked 待核实 must be reconfirmed on `microarch.org/micro59/` before being repeated as fact. ## 2026 cycle timeline (verified) | Gate | Date | Notes | |---|---|---| | Abstract registration | March 31, 2026, 11:59 PM EDT | Hard gate for paper upload | | Full paper | April 7, 2026, 11:59 PM EDT | HotCRP: `micro2026.hotcrp.com` | | Rebuttal / revision window | **June 3–17, 2026** | Two weeks — unusually long | | Notification | July 7, 2026 | | | Camera-ready | September 11, 2026 | | | Symposium | Oct 31 – Nov 4, 2026, Athens | | The eight-week gap between upload and rebuttal is when reviews are written; the three weeks after the window close is discussion and the decision meeting. ## What the process is known to enforce - **Double-blind, end to end.** Anonymity obligations persist through the rebuttal/revision window; artifact links stay anonymized the whole time. - **Format policing with teeth.** Submissions are inspected visually and automatically; violations can rej
- 2026 cycle timeline (verified)
- What the process is known to enforce
- What reviewers weigh in a microarchitecture paper
- Reading the outcome space
- Anatomy of a typical architecture review
- Leverage points for authors
- Calibrating expectations
- Output format
What does the micro-review-process skill do?
Use when reasoning about how a MICRO submission is judged — the double-blind HotCRP pipeline from the April deadline through the June rebuttal/revision window to the early-July notification, what reviewers score in a microarchitecture paper, the professional-conduct rules, and how the new Industry Track review differs.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill micro-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.