本文へ移動
cccskills
無料GitHub で公開

review-response

Systematic review response strategy guide for RebuttalStudio. Use when developing response strategies for reviewer comments, deciding how to classify concerns, or choosing between Accept/Defend/Clarify/Experiment approaches at any stage of the rebuttal pipeline.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md6.2 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Review Response Strategy Guide

RebuttalStudio Utility — Stage-General This skill applies across the full 5-stage rebuttal pipeline. It provides strategic guidance for classifying reviewer comments and choosing response approaches, complementing the stage-specific breakdown and refinement skills.

A systematic framework for analyzing reviewer comments and developing high-quality, professionally grounded rebuttal responses.


Comment Classification

Every reviewer comment belongs to one of four types. Identify the type before selecting a strategy.

TypeDescriptionExamples
MajorCore scientific or methodological concerns that affect the paper's conclusions"The baseline comparison is unfair", "The claims are unsupported by experiments"
MinorPeripheral concerns about presentation, wording, or supplementary experiments"Figure 3 is hard to read", "Missing ablation on X"
MisunderstandingReviewer has misread or misinterpreted the paper"The authors do not compare with Y" (but Y is in Table 2)
Typo / ClarityFactual errors, grammar, or unclear exposition"Definition 2 appears to be incorrect", "Section 3 is confusing"

Response Strategies

After classification, select the appropriate response strategy:

StrategyWhen to UseCore Approach
AcceptReviewer is correct; the concern is validAcknowledge explicitly, describe the change made, point to location
DefendReviewer's concern is based on a valid scientific disagreementProvide evidence, cite prior work, offer additional data if available
ClarifyReviewer has a misunderstanding that the paper actually addressesQuote the relevant section, explain why the concern does not apply
ExperimentReviewer requests additional empirical validationDescribe the experiment, provide preliminary results if possible

Core Principles

These apply to every response at every stage, from Stage 2 draft outlines to Stage 4 follow-up refinement:

  1. Acknowledge strengths before criticism — Thank reviewers for recognized contributions before addressing concerns. Even a brief acknowledgment improves tone.

  2. Anchor to evidence — Every claim in a response must be backed by: a paper section, a result in the supplementary, a cited prior work, or a new experiment. Do not assert without grounding.

  3. Address all concerns — An unreplied-to comment is treated by reviewers as evasion. Even a one-sentence acknowledgment is better than silence.

  4. No defensive language — Phrases like "the reviewer is incorrect" or "this criticism is unfounded" damage tone. Prefer collaborative phrasing: "We believe this may stem from…", "To clarify our intent…"

  5. Completeness over brevity — Concision matters, but do not sacrifice completeness. A reviewer who feels dismissed will lower the score.


Success Factors (from ICLR Spotlight Paper Analysis)

Key lessons distilled from analyzing accepted papers' rebuttals:

1. Acknowledge Strengths, Respond Positively to Criticism

  • Even spotlight papers receive constructive criticism
  • Reviewers are more receptive when they feel their positive observations were noted
  • Strategy: Lead with appreciation, then address each concern specifically

2. Provide Clarity and Intuitive Understanding

  • High-quality work can still have presentation gaps
  • Reviewers with different backgrounds may need extra scaffolding
  • Strategy: Expand explanations inline, move heavy derivations to appendix, add step-by-step walkthroughs where missing

3. Thorough Justification of Experimental Choices

  • Reviewers may question design decisions that seem obvious to the authors
  • Alternative metrics and ablations demonstrate rigor
  • Strategy: Justify each major choice; offer to add ablations if feasible within the rebuttal period

4. Address Ethics and Limitations Proactively

  • Especially important for sensitive application areas
  • Unaddressed limitations signal incomplete scholarship
  • Strategy: If a reviewer raises an ethical concern, respond directly with the paper's safeguards or discuss as a known limitation

5. Emphasize Practical Value and Scalability

  • Reviewers respond well to practical impact framing
  • Show that the contribution generalizes beyond the specific setting tested
  • Strategy: Add one or two sentences about broader applicability if not already present in the paper

Integration with RebuttalStudio Stages

StageHow to Use This Skill
Stage 1 — BreakdownAfter receiving reviewer text, apply the classification table to categorize each atomic issue before writing titles
Stage 2 — ReplyUse the Accept/Defend/Clarify/Experiment framework when drafting outlines; choose the strategy that matches each issue type
Stage 4 — Multi-RoundRe-apply classification to follow-up comments; use "Clarify" or "Experiment" strategy for reviewer persistence
Stage 5 — Final RemarksSummarize the response strategies used for each reviewer in the final remarks

Rebuttal Structure Template

For a well-structured per-reviewer rebuttal block:

We thank Reviewer [X] for their thoughtful and constructive feedback.

**Response to [Issue Title]**

> "[quoted reviewer comment]"

[Strategy: Accept / Defend / Clarify / Experiment]

[Response body: acknowledgment → direct answer → evidence → forward-looking note]

**Changes made**: [Section X, paragraph Y; or "no change needed because…"]

Adapted from Claude Scholar's review-response skill by gaoruizhang. Original: https://github.com/Galaxy-Dawn/claude-scholar/blob/main/skills/review-response/SKILL.md

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Verification guide for citations added during rebuttal writing. Use when Stage 2 responses introduce new references, when the Area Chair asks about a cited paper, or when any citation in the rebuttal might have been AI-generated. Prevents the serious credibility damage of fabricated references in reviewer-facing documents.

日本語の概要は準備中です。原文の説明を表示しています。

runtsang/RebuttalStudio2182026年4月4日 更新

Summarize extracted paper text into concise Markdown memory for later Stage 2 and Stage 4 background use, with fixed section headings and no fabricated claims.

日本語の概要は準備中です。原文の説明を表示しています。

runtsang/RebuttalStudio2182026年4月4日 更新

Systematic quality check for a completed rebuttal document before submission. Use after Stage 3 document compilation or after Stage 5 final remarks writing to verify completeness, tone, factual accuracy, and structural integrity. Catches common rebuttal errors before they reach reviewers.

日本語の概要は準備中です。原文の説明を表示しています。

runtsang/RebuttalStudio2182026年4月4日 更新

skills

無料

Multi-stage rebuttal analysis skill for RebuttalStudio. Use when organizing reviewer comments into stage-specific conference workflows, including stage1 breakdown, stage2 refinement, stage4 multi-round follow-up, and stage5 final remarks generation.

日本語の概要は準備中です。原文の説明を表示しています。

runtsang/RebuttalStudio2182026年4月4日 更新

Break down full ARR (ACL Rolling Review) reviewer responses into structured rebuttal units. Use when input contains ARR reviewer fields (Paper Summary, Strengths, Weaknesses, Comments/Suggestions) and numeric scores (Confidence, Soundness, Excitement, Overall Assessment, Reproducibility). Splits weaknesses and comments/suggestions into granular response items while preserving original wording for quoted issues.

日本語の概要は準備中です。原文の説明を表示しています。

runtsang/RebuttalStudio2182026年4月4日 更新

Base template for Stage1 reviewer-comment breakdown. Use when creating or extending conference-specific Stage1 skills (for example ICLR, ICML, NeurIPS, ACL) so shared extraction, splitting, and response-mapping logic stays consistent.

日本語の概要は準備中です。原文の説明を表示しています。

runtsang/RebuttalStudio2182026年4月4日 更新

runtsang のスキルをすべて見る

このスキルの問題を報告する