跳到主要内容
知仓学习社ZHICANG

ci-revision-and-response

Use when revising a Critical Inquiry (CI) essay after a decision and writing the response to readers and editors. CI acceptance typically follows au…

不碰外部(只输出文字)无严重或高危命中brycewang-stanford/Awesome-Journal-Skills

它会碰到什么

扫了多少1 个文本文件,5 KB
它会碰到什么不碰外部(只输出文字)
命中总数0 处
命中统计严重 0 · 高 0 · 中 0 · 低 0

这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。

技能内容

Revision & Response (ci-revision-and-response)

A request to revise from Critical Inquiry is an encouraging signal — acceptance typically **follows

author revisions, and the editors-in-chief read closely**. The revision must make the intervention

sharper and the readings more earned; the response letter must address every point while **protecting

the argument** that drew the invitation in the first place.

When to trigger

  • A decision arrived asking for revisions before (re)consideration
  • Readers' reports disagree and you must reconcile them
  • A reader asks for a change that would blunt the central claim
  • Writing the cover note to the editors summarizing the revision

Strategy

  1. Read the editors' letter as the rubric. The editors-in-chief signal which points are decisive;

solve those first. They adjudicate disagreements among readers.

  1. One point-by-point response, every comment addressed. Quote each comment, then respond — never

skip one; silence reads as non-compliance.

  1. Concede or argue, explicitly and with reasons. For each point: say what you changed and where

(section/page/figure), or disagree respectfully on grounds of argument, object, or theory.

Editors of a theory journal respect a well-argued disagreement over a hollow capitulation.

  1. Strengthen the intervention. Use the revision to make the claim bolder and clearer and the

readings deeper — resist changes that dilute the interdisciplinary stakes (see

ci-argument-and-intervention).

  1. Reconcile conflicting readers openly. When one reader wants the opposite of another, say so,

choose a principled path, and explain the tradeoff to the editors.

  1. Keep the apparatus in order. Hold the line on the 9,500-word cap (notes count), keep

Chicago footnotes clean, and confirm image permissions for any new figures (see

ci-citation-and-style, ci-submission).

Response-letter format

For each comment:

> [Quoted reader/editor comment]

Response: [What we did / why we respectfully disagree].
Change: [Section / page / figure number where the revision appears].

Open with a short summary of the main changes for the editors; group by reader; end each entry

with the location of every change so the editors can verify quickly.

Anti-patterns

  • Ignoring or quietly merging away a comment without a visible response
  • Capitulating to a request that breaks the argument just to please a reader
  • A defensive or dismissive tone toward readers
  • "We thank the reader" with no actual change or argued reason
  • Letting the revision spill past the word cap because notes were not counted
  • Adding new figures without clearing permissions

Operating pass for Critical Inquiry

Use this as a second-pass capability check. First lock the object, theoretical stakes, interpretive turn, and permission/citation discipline; then test whether the manuscript addresses humanities reviewers who expect a strong interpretive intervention rather than an empirical-results narrative.

  • Primary move: Return a claim-evidence-risk ledger; every recommendation must point to a manuscript location or missing artifact.
  • Decision ledger: return claim / evidence / blocker / next edit rows so the next pass can patch the manuscript directly.
  • Neighbor test: compare against PMLA for literary-field reach, New Literary History for theory/history, Representations for historically grounded cultural analysis; if the neighboring outlet has the stronger audience claim, recommend re-routing before polishing.
  • Verification floor: before submission-ready advice, re-open resources/official-source-map.md for volatile rules and name any live-check fact that could change the recommendation.

Output format

【Editors' decisive points】addressed first? [list]
【Coverage】every comment answered? [Y/N]
【Concede vs argue】each tagged with reason + change location
【Reader conflicts】reconciled and explained to editors? [Y/N]
【Intervention protected】no dilution of the claim/stakes? [Y/N]
【Apparatus】within cap, Chicago notes clean, new images cleared? [Y/N]
【Next】resubmit via Editorial Manager

Supplementary resources

  • [../../resources/official-source-map.md](../../resources/official-source-map.md) — review model and revision expectations
  • [../../resources/external_tools.md](../../resources/external_tools.md) — word-count rule, Chicago tooling, image specs

想直接用这个技能?

本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。