icde-review-process
Use when explaining or planning around IEEE ICDE peer review: the two-round-per-edition structure, area-chair-coordinated assignment with at least three reviewers, two-phase reviewing with a possible Revise & Resubmit, single-blind dynamics, how a builder-heavy committee reads a systems paper, and how outcomes feed IEEE Xplore.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-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.
# ICDE Review Process Use this to reason about review-stage strategy. Reopen the current call, important-dates page, and any reviewer instructions before making process claims; ICDE re-declares its review model each edition. ## Process model - ICDE takes research papers in **two rounds per edition** (ICDE 2027: ≈June and November). Each paper draws **at least three reviewers**, coordinated by an **area chair** who synthesizes the reviews into a recommendation. - The ICDE 2026 model ran **two reviewing phases** inside a round: the first phase returned **Revise & Resubmit, Accept, or Reject**; invited revisions were re-reviewed (≈4-week window) before a final **Accept/Reject**. Whether the current edition keeps the R&R phase is edition-specific (待核实). - Review is **single-blind**: reviewers see author identity; authors do not see reviewers. This changes the calculus — reputational priors exist, so the paper must earn belief on evidence, not on names. - A **Round 1 reject is terminal for the edition**; the paper cannot re-enter Round 2. That raises the stakes on getting the evaluation right the first time. - Accepted papers publish in **IEEE Xplore**; camera-ready compliance and IEEE
- Process model
- Who reviews here
- Scoring leverage table
- Stage-by-stage realism
- Output format
What does the icde-review-process skill do?
Use when explaining or planning around IEEE ICDE peer review: the two-round-per-edition structure, area-chair-coordinated assignment with at least three reviewers, two-phase reviewing with a possible Revise & Resubmit, single-blind dynamics, how a builder-heavy committee reads a systems paper, and how outcomes feed IEEE Xplore.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-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.