cvpr-review-process
Use when reasoning about how CVPR review actually works at 16,000-submission scale, covering the OpenReview pipeline and timeline, reviewer-duty enforcement and desk rejects, the reviewer LLM ban, AC and discussion dynamics, oral/highlight/poster decision tiers, and calibrating expectations to a ~25% acceptance rate.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cvpr-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.
# CVPR Review Process Use this to model what happens to a CVPR paper between upload and decision, and where author leverage exists. Every mechanism below is the 2026 cycle as verified 2026-07-08; scale numbers come from official CVPR program announcements. ## The machine, by the numbers The 2026 cycle put 16,092 submissions through full review (withdrawals and desk rejects excluded from that count) and accepted 4,090 — 25.42%. Doing that required roughly doubling the reviewer pool to 25,149 reviewers across 97 countries, coordinated by 909 area chairs. Two consequences follow for authors: - Your reviewers are statistically likely to include first-time CVPR reviewers (the pool doubled in one year; official training material exists for a reason). Write for a competent generalist in vision, not the five people in your subfield. - No individual paper gets much AC deliberation time by default. Papers that make the AC's job easy — clear claims, clean rebuttal, consistent reviews — get the benefit of scarce attention. ## Timeline anatomy (2026 cycle) | Phase | 2026 dates | What authors can do | |---|---|---| | Profile/abstract registration | Nov 6, 2025 | Fix profiles, finalize author lis
- The machine, by the numbers
- Timeline anatomy (2026 cycle)
- Enforcement culture: the distinctive part
- What a CVPR review contains
- Decision tiers
- After a rejection: mining reviews for signal
- Calibration for authors
- Reverify each cycle
- Output format
What does the cvpr-review-process skill do?
Use when reasoning about how CVPR review actually works at 16,000-submission scale, covering the OpenReview pipeline and timeline, reviewer-duty enforcement and desk rejects, the reviewer LLM ban, AC and discussion dynamics, oral/highlight/poster decision tiers, and calibrating expectations to a ~25% acceptance rate.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cvpr-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.