cav-review-process
Use when reasoning about how a CAV (Computer Aided Verification) submission is evaluated, covering the two-stage reviewing process (two reviews then an early-reject filter, then two more reviews with a rebuttal), the partial double-anonymity by category, the accept/reject outcome, the optional non-conditional artifact evaluation, and how CAV differs from TACAS and FMCAD.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-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.
# CAV Review Process Model the pipeline before interpreting any single review. CAV's process is a **two-stage filter**: a paper must survive the first two reviews before it reaches a rebuttal and the second pair of reviews. The most consequential mental shift for authors arriving from a single-round rebuttal conference is that **a paper can be rejected before the rebuttal ever happens** — so the first read has to stand on its own. ## Process model - Submission and review run on the CAV portal (EasyChair or HotCRP — **verify the live link**) with **partial double-anonymity**: Regular and Application papers are anonymized; Short Tool and Industrial Experience papers are not. - **Stage 1:** each paper receives **two** reviews. Papers with sufficient support proceed; the rest are **rejected early** (CAV 2026 tentative first-round outcome ~4 Mar 2026). - **Stage 2:** surviving papers receive **two additional** reviews and an **author-response (rebuttal)** window (CAV 2026: 30 Mar - 2 Apr 2026). - **Outcome:** accept or reject (CAV 2026 notification 17 Apr 2026). Accepted papers publish open access in **Springer LNCS**, and authors may then submit an artifact to the AEC on its own deadli
- Process model
- Reading a decision against the stages
- How CAV differs from its siblings
- Who reads you
- Where author leverage actually exists
- Reading a review packet
- Misreadings to avoid
- Output format
What does the cav-review-process skill do?
Use when reasoning about how a CAV (Computer Aided Verification) submission is evaluated, covering the two-stage reviewing process (two reviews then an early-reject filter, then two more reviews with a rebuttal), the partial double-anonymity by category, the accept/reject outcome, the optional non-conditional artifact evaluation, and how CAV differs from TACAS and FMCAD.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill cav-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.