vldb-review-process
Use when reasoning about how PVLDB reviewing actually works, covering the rolling monthly pipeline, the roughly six-week review turnaround, the accept/revise/reject outcome space, the one-shot revision's odds, single-blind dynamics, the volume review board, and how a VLDB decision differs from batch-deadline venues.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-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.
# VLDB Review Process Use this to set expectations after (or before) a PVLDB submission. The process is a journal pipeline wearing a conference badge: a standing review board for the volume, decisions on a monthly cadence, and a revision outcome with teeth. Details below were verified 2026-07-08 for Vols 19/20; the live guidelines page governs. ## The pipeline at a glance ```text 25th: abstract -> 1st: paper (5PM PT) -> ~15th next month: reviews + verdict | accept ---------------- 3 outcomes ---------------- reject | revise (one-shot) | up to 3 months -> revised paper -> same reviewers | accept or reject ``` Roughly six weeks from deadline to decision is the structural promise of the rolling model — competitive with any CS venue — and the price is that there is no rebuttal stage: your first chance to talk back is the revision, if offered. ## What each outcome means here | Outcome | Practical meaning | Your move | |---|---|---| | Accept | Publication in an upcoming monthly issue; conference slot at the matching VLDB | Camera-ready discipline (`vldb-camera-ready`) | | Revise | Reviewers believe a specific, listed set of fixes could flip them | Requirement ledger + three-month plan (`
- The pipeline at a glance
- What each outcome means here
- Who is reading
- Reading reviews on the monthly clock
- Contrast with batch venues
- Output format
What does the vldb-review-process skill do?
Use when reasoning about how PVLDB reviewing actually works, covering the rolling monthly pipeline, the roughly six-week review turnaround, the accept/revise/reject outcome space, the one-shot revision's odds, single-blind dynamics, the volume review board, and how a VLDB decision differs from batch-deadline venues.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill vldb-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.