rebuttal-and-response-to-reviewers
Plan and write responses to peer review, including journal "response to reviewers" letters for revise-and-resubmit, conference rebuttals under strict length limits (OpenReview/ICLR, NeurIPS, ICML, ACL ARR, CVPR), author responses to meta-reviews, and appeals. Use when a user receives reviews, must triage reviewer comments, draft point-by-point replies, decide what new experiments to run, disagree respectfully with a reviewer, or track manuscript changes for a revision. For authors answering reviews of their own manuscript; to write a review of someone else's paper, use peer-review instead.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- rebuttal-and-response-to-reviewers
- license
- MIT
- metadata
- { "tags": "peer review, rebuttal, response to reviewers, revise and resubmit, OpenReview, author response", "author": "Kalaris Labs (Sayan Chowdhury)", "version": "1.0", "category": "research-writing", "maintainer": "Kalaris Labs" }
- description
- Plan and write responses to peer review, including journal "response to reviewers" letters for revise-and-resubmit, conference rebuttals under strict length limits (OpenReview/ICLR, NeurIPS, ICML, ACL ARR, CVPR), author responses to meta-reviews, and appeals. Use when a user receives reviews, must triage reviewer comments, draft point-by-point replies, decide what new experiments to run, disagree respectfully with a reviewer, or track manuscript changes for a revision. For authors answering reviews of their own manuscript; to write a review of someone else's paper, use peer-review instead.
- compatibility
- No runtime dependencies.
03 SKILL.md 正文
Responding to Reviewers
The audience of a response is the editor or area chair, who must decide quickly whether concerns were addressed. Make every reply easy to verify: quote the concern, answer it directly, show the change with a location.
Step 1: Triage (before writing anything)
Split every review into atomic comments and classify each in a table:
| ID | Reviewer | Comment (short) | Type | Effort | Plan |
|---|---|---|---|---|---|
| R1.1 | 1 | Missing baseline X | Experiment | High | Run X on 2 datasets |
| R2.3 | 2 | Claim in §4 overstated | Wording | Low | Soften + add limitation |
Types: misunderstanding (the text was unclear), missing analysis/experiment, wording/presentation, disagreement on substance, out of scope, factual error by reviewer.
Then:
- Identify the 2-3 concerns that drive the scores (often shared across reviewers). These get the most effort and appear first in a conference rebuttal.
- Decide what is feasible in the revision window. Never promise experiments you will not run.
- Note conflicts between reviewers so the editor can adjudicate.
Step 2: Do the work, then write
Run the experiments and edit the manuscript before drafting replies, so every reply can point to a concrete change. Keep a change log with section/page/line numbers.
Step 3: Reply patterns
Journal response letter (no strict length):
Reviewer 1, Comment 1: "<quote or faithful summary of the concern>"
Response: We thank the reviewer for ... [direct answer in the first sentence].
We have [action]. The new results (Table 3, p. 7, lines 210-224) show ...
Change in manuscript: "<quoted new/revised text>" (Section 4.2, p. 7)
Best practices:
- Answer in the first sentence ("Yes, we have added...", "We agree and have...", "We respectfully disagree because...").
- Thanks once per reviewer, not before every comment.
- Quote revised text so the reviewer need not hunt for it. Provide a tracked-changes/diff version if the journal allows.
- Number comments (R1.1, R1.2 ...) and cross-reference instead of repeating ("see our response to R2.1").
Disagreeing (it is allowed and expected when justified):
- Acknowledge the underlying concern ("We understand the concern that ...").
- Give evidence: data, citations, a small additional analysis, or a precise explanation.
- Make a concession where honest: a clarification in the text or a stated limitation. Never be sarcastic, never say the reviewer "failed to understand". Rewrite the text so the next reader won't.
Conference rebuttal (hard limits: characters/words per reviewer or one page; check the venue):
- Lead with a short general response covering shared concerns and new results.
- Then per reviewer, only the comments that affect the decision, 2-5 sentences each.
- Put new numbers in compact tables. State exactly what will change in the camera-ready.
- Correct factual misreadings politely with pointers ("Section 3.2, Eq. 4 defines ...").
- Respect the venue's rules on new experiments, links and supplementary material. Many prohibit external links or new PDFs during rebuttal.
- On OpenReview discussions: reply promptly and concisely, and summarize the resolved points for the AC near the end.
Step 4: Cover note to the editor (journals)
Summarize the main changes in 3-6 bullets, flag any reviewer disagreements you could not resolve and why, and confirm all co-authors approved the revision.
Quality checklist
- Every comment has a response. Count them against the triage table.
- Every "we have added/changed" is actually in the manuscript at the cited location.
- New numbers match between response, manuscript, tables and abstract.
- Tone: professional, specific, never defensive. Read it as the reviewer would.
- No new claims beyond what the revised evidence supports.
- Length within the venue limit (count it).
Related skills
peer-review (reviewing others' work: useful to anticipate criticism), scientific-writing,
ml-paper-writing, scientific-critical-thinking, statistical-analysis.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.