ci-review-process
Use to understand how Critical Inquiry (CI) evaluates a submission — peer review plus close reading by the editors-in-chief in consultation with the editorial team, the no-simultaneous-submission rule, the commissioned/special-issue routes, and the high ambition bar that defines the journal. Sets expectations and shapes the essay to survive review; it does not contact editors.
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ci-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 (ci-review-process) Knowing how CI reads submissions lets you pre-empt the failure modes before sending. CI is **peer-reviewed**, and all peer-reviewed and commissioned manuscripts are **thoroughly reviewed by the editors-in-chief in consultation with the editorial team**. The decisive question is always the same: **is this a real intervention worthy of the journal's ambition bar?** ## When to trigger - Before submitting, to stress-test the essay against CI's expectations - Deciding whether your project is an unsolicited Article or a likely commissioned piece - Considering a special-issue proposal - Interpreting a decision and setting expectations ## How CI review works 1. **Editorial reading is central.** Beyond external referees, the **editors-in-chief read in consultation with the editorial team** — the essay must persuade serious generalist critics, not only subfield specialists. 2. **The ambition bar.** CI seeks "cutting-edge thought" and the "best critical thought in the arts and humanities." A competent, correct, but unsurprising essay is the typical non-fit — the journal wants an intervention (see `ci-argument-and-intervention`). 3. **Interdisciplinary legi
- When to trigger
- How CI review works
- Shape the essay to pass
- Anti-patterns
- Review-risk pass for Critical Inquiry
- Output format
- Supplementary resources
What does the ci-review-process skill do?
Use to understand how Critical Inquiry (CI) evaluates a submission — peer review plus close reading by the editors-in-chief in consultation with the editorial team, the no-simultaneous-submission rule, the commissioned/special-issue routes, and the high ambition bar that defines the journal. Sets expectations and shapes the essay to survive review; it does not contact editors.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill ci-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.