review-response-guide

Craft effective point-by-point reviewer response letters

191 stars

Best use case

review-response-guide is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Craft effective point-by-point reviewer response letters

Teams using review-response-guide should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/review-response-guide/SKILL.md --create-dirs "https://raw.githubusercontent.com/wentorai/research-plugins/main/skills/research/paper-review/review-response-guide/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/review-response-guide/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How review-response-guide Compares

Feature / Agentreview-response-guideStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Craft effective point-by-point reviewer response letters

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# Review Response Guide

A skill for crafting effective, professional point-by-point response letters to peer reviewer comments. Covers response letter structure, strategies for different types of reviewer feedback, prioritization of revisions, managing conflicting reviewer opinions, and navigating the revision-resubmission cycle to maximize acceptance probability.

## Response Letter Architecture

### Structural Template

A well-organized response letter follows a consistent structure that makes it easy for editors and reviewers to verify that all concerns have been addressed.

```
Response Letter Structure:

1. COVER LETTER TO EDITOR (1 page max)
   - Thank the editor and reviewers
   - Summarize the 3-5 most significant changes
   - Highlight any points where you respectfully disagree
   - Note if conflicting reviewer requests required a judgment call
   - State that all changes are marked in the revised manuscript

2. SUMMARY OF CHANGES (optional but recommended)
   - Bulleted list of all major changes
   - Brief enough to read in 2 minutes
   - Organized by theme, not by reviewer

3. POINT-BY-POINT RESPONSES
   For each reviewer, for each comment:

   ---
   REVIEWER [N], Comment [M]:

   [Quote the reviewer's comment verbatim, italicized]

   RESPONSE:
   [Your substantive response]

   CHANGES MADE:
   [Exact description of what changed, with page/line numbers
    or quoted text from the revised manuscript]
   ---

4. ADDITIONAL CHANGES (if any)
   - Changes you made that were not requested by reviewers
   - Example: "We also updated Figure 3 to use colorblind-
     friendly colors throughout."
```

### Formatting Best Practices

```
Visual formatting for clarity:

1. Use consistent fonts:
   - Reviewer comments: italic
   - Your responses: regular weight
   - Changes made: indented or in a different color

2. Numbering system:
   - R1.1, R1.2, R1.3 for Reviewer 1's comments
   - R2.1, R2.2 for Reviewer 2's comments
   - Major comments first, then minor comments

3. Cross-references:
   - When one response addresses multiple comments:
     "See our response to R1.3 above, which also addresses
      this concern."
   - When changes span multiple sections:
     "See revised manuscript, pp. 8-9, paragraphs 2-3
      (marked in blue)."

4. Length calibration:
   - Major comments: 100-300 words per response
   - Minor comments: 20-50 words per response
   - Total response letter: typically 5-20 pages
   - Longer is fine if substantive; never pad with fluff
```

## Response Strategies by Comment Type

### Methodological Concerns

```
When reviewers question your methodology:

Scenario: "The sample size is too small for the claims made."

Strong response structure:
1. Acknowledge the concern explicitly
2. Provide quantitative justification (power analysis)
3. Add additional analysis if possible
4. Acknowledge remaining limitations honestly

Example:
"We appreciate this important concern about statistical power.
We have now added a formal power analysis (Supplementary
Section S2) showing that our sample of N=120 provides 82%
power to detect the medium effect size (d=0.5) that our
hypotheses predicted, based on prior work by Chen et al.
(2021). Our observed effects were larger than this threshold
(d=0.72, 95% CI [0.41, 1.03]). We have also added a
sensitivity analysis (new Table S3) confirming that results
are robust to different analytical choices. We acknowledge
the power limitation for detecting small effects and have
added this to the Limitations section (p. 18, lines 4-8)."
```

### Requests for Additional Analysis

```
When reviewers ask for more analysis:

If feasible - do it:
  "We thank the reviewer for this excellent suggestion.
   We have conducted the requested analysis and present
   the results in new Table 4 (p. 12). The findings are
   consistent with our main results, strengthening our
   conclusions."

If partially feasible - do what you can:
  "We have conducted [part A] of the suggested analysis
   (new Figure S5). Unfortunately, [part B] is not possible
   with our current dataset because [specific reason].
   We have added this as a direction for future research
   (p. 19, line 12)."

If not feasible - explain clearly:
  "This analysis would require [data/resource] that is not
   available in our study because [reason]. However, we have
   conducted [alternative analysis] that addresses the
   underlying concern. We also now discuss this limitation
   explicitly (p. 17)."
```

### Contradictory Reviewer Requests

```
When Reviewer 1 and Reviewer 2 disagree:

This happens frequently. The key is to:
1. Acknowledge both perspectives
2. Explain your reasoning transparently
3. Ask the editor to adjudicate if needed

Example:
"Reviewer 1 suggests removing the qualitative analysis
(R1.4), while Reviewer 2 asks us to expand it (R2.7).
We believe the qualitative component adds important
context to our quantitative findings, consistent with
mixed-methods best practices (Creswell, 2018). We have
therefore retained the qualitative analysis but tightened
it from 4 pages to 2 pages, focusing on the most
illustrative quotes. We respectfully ask the editor to
advise if further adjustment is needed."

In the cover letter:
"We note a point of divergence between Reviewers 1 and 2
regarding the qualitative analysis (R1.4 vs R2.7). We have
described our proposed compromise in the detailed responses
and welcome the editor's guidance on this matter."
```

## Handling Difficult Reviews

### When a Reviewer Is Factually Wrong

```
Strategy: Correct respectfully, blame your own writing

Never: "The reviewer is incorrect about..."
Never: "The reviewer failed to understand..."
Never: "As any expert in this field would know..."

Instead:
"We appreciate this comment, which indicates that our
description of [topic] was not sufficiently clear. We have
rewritten Section 3.2 (pp. 9-10) to clarify that [correct
information]. The key point, which we now state explicitly
in the second paragraph, is that [clarification]. We hope
the revised text prevents this misunderstanding."

Why this works:
- Acknowledges the reviewer's effort
- Takes responsibility for the miscommunication
- Improves the paper for future readers who might have
  the same misunderstanding
- Corrects the record without antagonizing the reviewer
```

### When a Review Is Hostile or Unfair

```
Strategy: Maintain professionalism, address substance

If a comment is dismissive without substance:
  Reviewer: "This paper is not interesting."
  Response: "We have revised the Introduction to more
  clearly articulate the significance of our research
  question and its implications for [field]. Specifically,
  we now explain [relevance point 1], [relevance point 2],
  and [relevance point 3] (pp. 2-3)."

If a comment reveals the reviewer did not read the paper:
  Reviewer: "The authors did not control for age."
  Response: "We appreciate this concern. Age was included
  as a covariate in all models, as described in Section 3.4
  (p. 11, line 3) and reported in Table 2, Column 3. We have
  added bold formatting to make this control variable more
  visible in the table."

If appropriate, raise concerns with the editor:
  In the cover letter (not the response):
  "We note that Comment R2.5 appears to request an analysis
  that is already reported in Table 4 of our manuscript.
  We welcome the editor's assessment of whether our response
  adequately addresses this concern."
```

## Revision Workflow

### Organizing the Revision Process

```
Step-by-step revision workflow:

1. Cooling-off period (1-2 days):
   Read reviews once, then set them aside.
   Initial emotional reactions are normal.

2. Comment triage (1 day):
   Create a spreadsheet with columns:
   - Reviewer, Comment number, Category, Difficulty, Action
   Categories: major/minor, methodological/theoretical/editorial
   Difficulty: easy/medium/hard

3. Easy wins first (1-2 days):
   Address minor comments: typos, formatting, missing references
   These require minimal thought and build momentum

4. Hard problems (1-2 weeks):
   Address major methodological and theoretical concerns
   Run additional analyses
   Rewrite substantial sections
   Consult co-authors on strategy

5. Response letter drafting (2-3 days):
   Write point-by-point responses
   Include specific page/line numbers for all changes

6. Co-author review (3-5 days):
   All co-authors review the revised manuscript AND the
   response letter before resubmission

7. Final checks (1 day):
   Verify all page/line numbers are correct
   Check that tracked changes match response descriptions
   Ensure formatting meets journal requirements

Timeline: Allow 4-8 weeks for a major revision
Deadline: Most journals give 60-90 days; request extension
if needed (editors almost always grant it)
```

A well-crafted response letter demonstrates intellectual maturity, thoroughness, and respect for the peer review process. The strongest response letters share a common trait: they treat every reviewer comment as an opportunity to improve the paper, even when the reviewer is wrong, because the revision process ultimately serves the reader.