Agent skill · Code Review & Quality

iros-review-process

Use when reasoning about IROS peer review — the PaperPlaza Associate-Editor/Editor pipeline, the traditional no-rebuttal single-notification model, how the video and embodied evidence steer reviewers, the 2026 double-anonymous posture, decision criteria for systems papers, and IEEE Xplore proceedings outcomes.

brycew6m878★ · +32/wk · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-review-process --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: IROS-Skills/skills/iros-review-process/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 909 · +31 this week
Language: Stata
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# IROS Review Process Use this to reason about review-stage strategy. Reopen the current CFP, PaperPlaza instructions, and any reviewer guidelines before making process claims — IROS review mechanics are set per edition by the co-sponsoring IEEE/RSJ committee. ## Process model - Submission and review run on **PaperPlaza**. Papers are handled by an **Associate Editor** under an **Editor**, who assign and synthesize reviews; there is no standing editor-in-chief for the conference. - Reviewers are **embodied-systems researchers**. They weigh hardware, task distributions, trial counts, failure analysis, and sim-to-real honesty at least as much as a clean plot. - The **video is read as evidence**: many reviewers watch it before the text, so a weak or misleading video colors the whole review. - The **2026 cycle is double-anonymous**; author identity should not be inferable from text, figures, or video. - Accepted papers go to **IEEE Xplore**, so camera-ready compliance and the copyright form matter as much as the initial decision. ## The no-rebuttal consequence IROS has traditionally delivered **reviews together with the decision and no author-response phase**. This changes strategy fund

What's inside
Steps it walks through
  1. Process model
  2. The no-rebuttal consequence
  3. Scoring leverage table
  4. Stage-by-stage realism
  5. Reject-to-next-venue realism
  6. Output format
More from Awesome-Journal-Skills
All skills →
About this skill
What does the iros-review-process skill do?

Use when reasoning about IROS peer review — the PaperPlaza Associate-Editor/Editor pipeline, the traditional no-rebuttal single-notification model, how the video and embodied evidence steer reviewers, the 2026 double-anonymous posture, decision criteria for systems papers, and IEEE Xplore proceedings outcomes.

How do I install it?

Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill iros-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.

Keep going