Peer Review
spacering-net/codeg
Structured manuscript/grant review with checklist-based evaluation.
A skill your agent uses 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…
Install Icde Review Process
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-review-process -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icde-review-process --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ICDE-Skills/skills/icde-review-process .claude/skills/icde-review-process && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "icde-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDE-Skills/skills/icde-review-process into .claude/skills/icde-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icde-review-process", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDE-Skills/skills/icde-review-processType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-review-process -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icde-review-process --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/ICDE-Skills/skills/icde-review-process .agents/skills/icde-review-process && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "icde-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDE-Skills/skills/icde-review-process into .agents/skills/icde-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icde-review-process", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-review-process -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icde-review-process --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/ICDE-Skills/skills/icde-review-process .cursor/skills/icde-review-process && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "icde-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDE-Skills/skills/icde-review-process into .cursor/skills/icde-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icde-review-process", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/brycewang-stanford/Awesome-Journal-Skills.git --path ICDE-Skills/skills/icde-review-process--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-review-process -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icde-review-process --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/ICDE-Skills/skills/icde-review-process .gemini/skills/icde-review-process && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "icde-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDE-Skills/skills/icde-review-process into .gemini/skills/icde-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icde-review-process", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icde-review-processInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-review-process -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/ICDE-Skills/skills/icde-review-process .github/skills/icde-review-process && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "icde-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDE-Skills/skills/icde-review-process into .github/skills/icde-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icde-review-process", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-review-process -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install brycewang-stanford/Awesome-Journal-Skills icde-review-process --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/ICDE-Skills/skills/icde-review-process .opencode/skills/icde-review-process && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "icde-review-process" agent skill from https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/ICDE-Skills/skills/icde-review-process into .opencode/skills/icde-review-process/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "icde-review-process", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
icde-review-process- GitHub stars
- 1.2k
- Token cost
- ~1k tokens
- SKILL.md length
- 456 words
- Files
- 1
- Skills in repo
- 2,387
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses 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…
- Planning around IEEE ICDE peer review: the two-round-per-edition structure
- SKILL.md covers Process model, Who reviews here, Scoring leverage table and Stage-by-stage realism, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Area-chair-coordinated assignment with at least three reviewers
What it does
Icde Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Research & Science, covering Peer review. The repository describes itself as: Journal-specific Claude Code/Codex skill packs covering mainstream journals — AER, QJE, Nature, Cell, 管理世界, 经济研究 & 200+ more — your fast track to getting published. ｜ 覆盖主流期刊的… The licence is MIT.
When your agent uses it
- 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
Example prompts
- “/icde-review-process”
What it can do on your machine
Read from SKILL.md and the folder at commit 932eb23. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Icde Review Process loads about 1k tokens when it runs. Until then it costs about 87 tokens; SKILL.md has 456 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from brycewang-stanford/Awesome-Journal-Skills at commit 932eb23, republished under its MIT licence (© brycewang-stanford). 456 words, ~1,002 tokens.
Download SKILL.mdSave it as
.claude/skills/icde-review-process/SKILL.md (or your agent's skills folder).- name
- icde-review-process
- description
- 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.
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 metadata matter as much as the acceptance itself.
Who reviews here
- The committee is builder-heavy: reviewers who have implemented indexes, optimizers, and storage engines. They read an evaluation the way an engineer reads a benchmark — skeptical of untuned baselines, single-point results, and hidden costs.
- Because scope overlaps SIGMOD and VLDB, at least one reviewer will likely know the nearest prior system intimately; a novelty claim that ignores it is caught, not skimmed past.
- Borderline systems papers usually fail on one of three edges: an untuned or unfair baseline, a performance claim with no operating point, or a mechanism whose benefit is never isolated by an ablation.
Show full SKILL.md (176 more words)Show less
Scoring leverage table
| Review dimension | What raises it | What sinks it |
|---|---|---|
| Novelty | A named mechanism a builder could not have trivially derived | "Yet another index" with no isolable new idea |
| Evaluation | Tuned baselines, scale curves, variance, disclosed cost | Single-point wins on one synthetic workload |
| Soundness | Ablations that isolate the mechanism's contribution | Gains that could come from unrelated engineering |
| Reproducibility | Runnable supplement whose availability is evident | Empty or unrunnable supplemental material |
| Significance | A primitive an ecosystem can adopt | A narrow tweak with no downstream reach |
Stage-by-stage realism
- Phase 1 reviews: read them as the area chair will — is the central evaluation objection answerable? A Revise & Resubmit is an opportunity, not a soft reject; treat the requirement list as binding.
- Revision re-review: the same reviewers check the list; unrequested scope changes hurt.
- Decision: one unresolved fairness or cost objection outweighs several resolved clarity nits, because a builder-heavy committee anchors on the evaluation.
- Round choice as strategy: since Round 1 rejects skip the edition, aiming an immature evaluation at the earlier round is a common self-inflicted loss.
Output format
[Current stage] submitted / phase-1 reviews / revision / decision / camera-ready
[Round] Round 1 or Round 2 (edition)
[Decision actors] <reviewers / area chair / program chairs>
[Likely leverage] <novelty / evaluation / soundness / reproducibility>
[Central objection] <the one thing the area chair will weigh most>
[Next response move] <one action>© brycewang-stanford, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in ICDE-Skills/skills/icde-review-process of brycewang-stanford/Awesome-Journal-Skills.
Open the folder on GitHubat commit 932eb23
Compare with similar skills
Icde Review Process next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Icde Review Process this skillbrycewang-stanford/Awesome-Journal-Skills | 1.2k | — | ~1k | Automated safety check: Pass | MIT | |
| Peer Reviewspacering-net/codeg | 3.9k | 17 repos | ~5.9k | Automated safety check: Notes | MIT | |
| Scholar Evaluationspacering-net/codeg | 3.9k | 11 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Academic Paper Writing PipelineImbad0202/academic-research-skills | 51k | — | ~16k | Automated safety check: Pass | Custom licence | |
| Academic Paper ReviewerImbad0202/academic-research-skills | 51k | — | ~11k | Automated safety check: Pass | Custom licence | |
| Peer ReviewK-Dense-AI/claude-scientific-writer | 2.4k | 2 repos | ~3.1k | Automated safety check: Notes | MIT |
Similar skills
Scholar Evaluation
spacering-net/codeg
Systematically evaluate scholarly work using the ScholarEval framework, providing structured assessment across research quality dimensions including problem formulation, methodology, analysis, and…
Academic Paper Writing Pipeline
Imbad0202/academic-research-skills
Runs a 12-agent pipeline that plans, drafts, cites, reviews and formats academic papers, with modes for revision, rebuttals, abstracts and citation checks.
Academic Paper Reviewer
Imbad0202/academic-research-skills
Simulates a journal peer review of a manuscript with a five-seat reviewer panel, an editorial synthesizer and several review modes.
Peer Review
K-Dense-AI/claude-scientific-writer
Prepare evidence-bounded, constructive peer-review drafts and structured manuscript assessments.
Academic Research Pipeline
Imbad0202/academic-research-skills
Orchestrates a ten-stage academic workflow from research to finished manuscript, including integrity checks, two rounds of peer review and revision.
More from brycewang-stanford/Awesome-Journal-Skills
All 2,387 skills in this repoAaag Data Analysis
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running and reporting the analysis for an Annals of the American Association of Geographers manuscript — spatial statistics and modeling, remote-sensing accuracy, or…
Aaag Literature Positioning
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when positioning an Annals of the American Association of Geographers manuscript in the literature — engaging geographic scholarship across the relevant area and the…
Aaag Rebuttal
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when responding to an Annals of the American Association of Geographers decision letter (major/minor revision) — building a point-by-point response to the subject editor and…
Aaag Research Design
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when defending the research design of an Annals of the American Association of Geographers manuscript — spatial/quantitative analysis and GIScience, remote-sensing and…
Aaag Review Process
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when you need to understand how the Annals of the American Association of Geographers evaluates a manuscript — double-anonymous review routed through a subject editor by…
Aaag Submission
brycewang-stanford/Awesome-Journal-Skills
A skill your agent uses when running the final pre-submission preflight for the Annals of the American Association of Geographers via ScholarOne Manuscripts — area/article-type selection…
Related
Categories
Questions about Icde Review Process
What does Icde Review Process do?
A skill your agent uses 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…. Icde Review Process is an agent skill from brycewang-stanford/Awesome-Journal-Skills. 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.
When should I use Icde Review Process?
Icde Review Process fits situations like: 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 do I install Icde Review Process in Claude Code?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-review-process -a claude-code`. Or copy the skill folder (ICDE-Skills/skills/icde-review-process in brycewang-stanford/Awesome-Journal-Skills) into .claude/skills/icde-review-process in your project. Claude Code loads it when a task matches its description.
How do I install Icde Review Process in Codex?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-review-process -a codex`. Or copy the skill folder (ICDE-Skills/skills/icde-review-process in brycewang-stanford/Awesome-Journal-Skills) into .agents/skills/icde-review-process in your project. Codex loads it when a task matches its description.
Can I use Icde Review Process in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-review-process -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/icde-review-process, .gemini/skills/icde-review-process, .github/skills/icde-review-process and .opencode/skills/icde-review-process in your project.
What does Icde Review Process need to run?
SKILL.md names no scripts, command-line tools or credentials: Icde Review Process is instructions for the agent only.
Does Icde Review Process access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Icde Review Process safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Icde Review Process use?
Icde Review Process is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Icde Review Process use?
About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Icde Review Process?
Skills that share tags, products or a category with Icde Review Process: Peer Review (spacering-net/codeg, 3.9k stars), Scholar Evaluation (spacering-net/codeg, 3.9k stars), Academic Paper Writing Pipeline (Imbad0202/academic-research-skills, 51k stars) and Academic Paper Reviewer (Imbad0202/academic-research-skills, 51k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Icde Review Process?
brycewang-stanford (a GitHub user) maintains it in brycewang-stanford/Awesome-Journal-Skills, which has 1,231 GitHub stars. The repository holds 2,387 skills in this directory. The repository was last updated on September 27, 2026.
Source: brycewang-stanford/Awesome-Journal-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.