ijoc-review-process
Use when calibrating expectations for the INFORMS Journal on Computing (IJOC) review cycle — the Area-Editor desk-reject gate, the undisclosed associate editor, single-blind reviewing, decision types, and whether a sibling journal fits better. Sets expectations and strategy; it does not draft the rebuttal (see ijoc-rebuttal).
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ijoc-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.
# Review Process (ijoc-review-process) ## When to trigger - You are about to submit and want to understand the **gates** and likely timeline - A submission has been silent and you are unsure where it sits in the IJOC pipeline - A decision arrived (reject / major / minor) and you need to read it correctly before responding - You are weighing whether IJOC or a **sibling** (Operations Research, Management Science, MPC, IJOO) is the better home after a tough first round ## How the IJOC pipeline actually works The cycle has a structure worth planning around (检索于 2026-06；以官网为准): 1. **Area-Editor suitability gate.** Your chosen technical area routes the paper to an **Area Editor** who first judges fit. Roughly **40% are desk-rejected** here for being out of scope, computing-light, or mismatched to the area. This gate rewards the `ijoc-topic-selection` and `ijoc-contribution-framing` work: an Area Editor who cannot see the computational advance in the abstract and intro will not send it out. 2. **Associate-editor handling — blind to you.** Survivors are assigned an **associate editor who manages the review and whose identity is never revealed** to authors. You cannot tailor a response to "
- When to trigger
- How the IJOC pipeline actually works
- Reading an IJOC decision letter
- Sibling fit after a hard round
- Checklist
- Anti-patterns
- Output format
What does the ijoc-review-process skill do?
Use when calibrating expectations for the INFORMS Journal on Computing (IJOC) review cycle — the Area-Editor desk-reject gate, the undisclosed associate editor, single-blind reviewing, decision types, and whether a sibling journal fits better. Sets expectations and strategy; it does not draft the rebuttal (see ijoc-rebuttal).
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ijoc-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.