iccv-review-process
Use when reasoning about ICCV's review pipeline and where authors have leverage, covering the March-to-June OpenReview timeline, the every-author-reviews contract and its 2025 desk-reject enforcement, the reviewer LLM prohibition, decision statistics at 24% acceptance, oral and Highlight tiers, and the post-decision Findings outlet.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-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.
# ICCV Review Process This models what happened to a paper inside the ICCV 2025 pipeline — the most recent completed cycle, verified 2026-07-08 — and what an author can and cannot influence at each stage. The 2027 chairs may restructure any of it (待核实 once the Hong Kong cycle posts its pages). ## Pipeline at a glance (2025 anchors) ```text Mar 3 registration closes (abstract, authors, profiles) Mar 7 paper + supplement due (one event, 11:59pm HST) Mar–May assignment and reviewing; authors serve as reviewers in parallel May 9 reviews released to authors May 10–16 one-page rebuttal window May–Jun reviewer/AC discussion and meta-review (authors silent) late Jun decisions (2025 statistics: 11,239 valid submissions, 2,699 accepted, 24%) Oct 19–23 conference, Honolulu (workshops 19–20, main program 21–23) ``` Between March and May the same lab members are usually on both sides of the table, because ICCV 2025 required **every author** to review unless exempted (exemptions covered people new to or outside the vision community). Model your own reviewers accordingly: they are authors from the same submission wave, mostly competent, uniformly overloaded, and reading your paper between their o
- Pipeline at a glance (2025 anchors)
- Enforcement, with 2025 receipts
- The LLM line
- What the decision distribution looked like
- After the decision: the 2025-specific outlet
- Where authors have zero leverage
- Reverify each cycle
- Output format
What does the iccv-review-process skill do?
Use when reasoning about ICCV's review pipeline and where authors have leverage, covering the March-to-June OpenReview timeline, the every-author-reviews contract and its 2025 desk-reject enforcement, the reviewer LLM prohibition, decision statistics at 24% acceptance, oral and Highlight tiers, and the post-decision Findings outlet.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-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.