colm-review-process
Use when reasoning about how COLM reviews a paper — the OpenReview pipeline from late-March submission through the May review release, the May-June rebuttal window, July decisions, reciprocal-reviewing obligations, the LLM-use rules for reviewers, and how a three-edition-old venue's norms differ from mature conferences.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-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.
# COLM Review Process COLM runs a compact, single-cycle-per-year pipeline on OpenReview, and — because the venue is three editions old — its reviewing culture is still visibly under construction. Understanding both the posted mechanics and the young-venue dynamics is what lets authors time their effort correctly. ## The 2026 pipeline (verified 2026-07-08) | Phase | 2026 dates | Author-side reality | |---|---|---| | Abstract deadline | March 26 | Drives bidding and reviewer matching | | Full paper deadline | March 31 | Submission freezes | | Review writing | April - mid-May | Silence; nothing actionable | | Reviews released | May 22 | Read-only day one; no same-day replies | | Rebuttal | May 22 - June 8 | The 18-day window where effort pays | | AC discussion + decisions | June - July 8 | Decisions posted July 8 | | Camera-ready | August 7 | Accepted papers finalize | | Conference | October 6-9, San Francisco | Main program Oct 6-8, workshops Oct 9 | On this pack's access date — July 8, 2026 — the pipeline is at its decision moment: rebuttals are closed and notifications land today. If you are triaging an outcome, go directly to `colm-camera-ready` (accept) or the resubmission logic
- The 2026 pipeline (verified 2026-07-08)
- Who reviews you, and why it feels different
- Rules that govern the conversation
- Reading a COLM review packet
- What the AC actually reads
- If the decision is a reject
- Volatile every edition
- Output format
What does the colm-review-process skill do?
Use when reasoning about how COLM reviews a paper — the OpenReview pipeline from late-March submission through the May review release, the May-June rebuttal window, July decisions, reciprocal-reviewing obligations, the LLM-use rules for reviewers, and how a three-edition-old venue's norms differ from mature conferences.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill colm-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.