iccv-camera-ready
Use when an ICCV paper is accepted and the final version, releases, and October conference must be delivered, covering de-anonymization edits, the summer camera-ready window between June decisions and the autumn meeting, CVF open access plus IEEE Xplore publication, arXiv synchronization after the embargo lifts, and presenting at an international venue.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-camera-ready --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 Camera-Ready Acceptance at ICCV opens an unusually long runway: decisions landed in late June 2025 and the conference ran October 19–23 in Honolulu, leaving roughly four months between verdict and podium. The camera-ready deadline sits inside that window (the exact 2025 date was not fetchable at verification time — 待核实; it is communicated in the acceptance email and on the conference site). Use the runway deliberately: most camera-ready damage happens in the first rushed week, and most release-promise damage in the last. ## The publication pair An ICCV paper is published through two channels with different jobs: | Channel | What it is | What depends on it | |---|---|---| | CVF open access (openaccess.thecvf.com) | Free public copy of the accepted paper, posted around the conference | What the field actually reads and cites day-to-day | | IEEE Xplore | Version of record under IEEE co-sponsorship | Institutional/indexing records, some tenure and reporting systems | No article-processing charge exists in this pipeline; costs run through registration. There is also no copy editor: the PDF you upload is what both channels carry forever, so the proofreading pass below is the only
- The publication pair
- De-anonymization is a rewrite pass, not a toggle
- Numbers that changed since review
- Synchronizing the public copies
- October in another country
- Final-version defect list
- Reverify for the current cycle (all 待核实 for 2027)
- Output format
Promise-tracking during the camera-ready edit
grep -oiE 'we will [a-z ]+' rebuttal.pdf.txt | sort -u > promises.txt
awk 'END{print NR" promises to verify"}' promises.txt
pdftotext camera_ready.pdf - | grep -nE '\?\?|Anonymous|under review' | head # broken refs & leftoversWhat does the iccv-camera-ready skill do?
Use when an ICCV paper is accepted and the final version, releases, and October conference must be delivered, covering de-anonymization edits, the summer camera-ready window between June decisions and the autumn meeting, CVF open access plus IEEE Xplore publication, arXiv synchronization after the embargo lifts, and presenting at an international venue.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iccv-camera-ready --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.