rebuttal-writing-guide
Write effective rebuttals to reviewer comments for journal submissions
Best use case
rebuttal-writing-guide is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Write effective rebuttals to reviewer comments for journal submissions
Teams using rebuttal-writing-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
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/rebuttal-writing-guide/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How rebuttal-writing-guide Compares
| Feature / Agent | rebuttal-writing-guide | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Write effective rebuttals to reviewer comments for journal submissions
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.
SKILL.md Source
# Rebuttal Writing Guide
A skill for writing effective, professional responses to reviewer comments during the peer review revision process. Covers response letter structure, strategies for addressing criticism constructively, handling unfair reviews, and organizing major revisions.
## Response Letter Structure
### Standard Format
```
Response Letter Template:
Dear Editor and Reviewers,
Thank you for your thoughtful review of our manuscript
"[Title]" (Manuscript ID: [ID]). We appreciate the
constructive feedback and have carefully addressed all
comments. Below, we provide point-by-point responses.
Major changes include:
- [Summary of change 1]
- [Summary of change 2]
- [Summary of change 3]
In the revised manuscript, all changes are highlighted in blue.
---
RESPONSE TO REVIEWER 1
Comment R1.1: [Exact quote of reviewer comment]
Response: [Your response]
Changes made: [Description of what was changed and where]
---
Comment R1.2: [Next comment]
...
RESPONSE TO REVIEWER 2
...
```
### Formatting Best Practices
```python
def format_response(reviewer_num: int, comment_num: int,
comment: str, response: str,
changes: str = None) -> str:
"""
Format a single reviewer response entry.
Args:
reviewer_num: Reviewer number (1, 2, 3...)
comment_num: Comment number within this reviewer
comment: The reviewer's original comment (verbatim)
response: Your response
changes: Description of manuscript changes made
"""
entry = (
f"**Comment R{reviewer_num}.{comment_num}:**\n"
f"*{comment}*\n\n"
f"**Response:**\n{response}\n"
)
if changes:
entry += f"\n**Changes made:** {changes}\n"
return entry
```
## Response Strategies
### Handling Different Comment Types
```
Agreement (easiest -- just do it):
Reviewer: "Table 2 should include confidence intervals."
Response: "We agree. We have added 95% confidence intervals to
Table 2 (see revised manuscript, p. 12)."
Partial agreement (do what you can, explain what you cannot):
Reviewer: "The authors should include 5 additional control variables."
Response: "We appreciate this suggestion. We have added controls for
age and income, which are theoretically motivated (p. 15).
We could not include education, occupation, and region
because [specific reason]. However, we now discuss this
limitation in Section 5.2."
Respectful disagreement (provide evidence):
Reviewer: "The sample is too small to draw any conclusions."
Response: "We understand this concern. However, our power analysis
(now included as Supplementary Table S1) shows that our
sample of N=85 provides 80% power to detect a medium
effect (d=0.5) at alpha=0.05. Furthermore, our primary
effect sizes were large (d=0.8-1.2), well above the
detectable threshold. We have added this justification
to Section 3.1 (p. 8)."
```
### Golden Rules for Rebuttals
```
DO:
- Thank reviewers (sincerely, not sarcastically)
- Address EVERY comment, even minor ones
- Quote the reviewer's comment verbatim before responding
- Be specific about what changed and where (page/section numbers)
- Provide evidence for disagreements (citations, analyses, data)
- Run additional analyses when requested if feasible
- Use a respectful, professional tone throughout
- Keep responses concise but thorough
DO NOT:
- Ignore any comment (even if trivial)
- Be defensive or dismissive
- Argue from authority ("We are experts in this area")
- Lie about changes you did not actually make
- Attack the reviewer's competence
- Submit essentially the same manuscript with a new cover letter
```
## Handling Difficult Reviews
### When a Reviewer Is Wrong
```
Situation: The reviewer misunderstood your method.
Strategy: Clarify without blaming the reviewer.
Bad: "The reviewer clearly did not read our paper carefully."
Good: "We appreciate this comment and recognize that our
description of the method may not have been sufficiently
clear. We have rewritten Section 3.2 to clarify that
[explanation]. The key distinction is [point], which we
now make explicit on p. 10."
```
### When a Reviewer Requests Impossible Changes
```
Situation: The reviewer asks for data you do not have.
Strategy: Acknowledge, explain constraints, offer alternatives.
Response: "This is an excellent suggestion that would strengthen
the study. Unfortunately, our dataset does not include
[variable] because [reason]. As an alternative, we have
[what you did instead]. We have also added this as a
limitation and future direction (Section 5.3, p. 18)."
```
## Organizing a Major Revision
### Workflow for Revision
```
1. Read ALL reviews completely before making any changes
2. Create a spreadsheet categorizing each comment:
- Reviewer, comment number, category, difficulty, action
3. Address easy changes first (typos, formatting, missing refs)
4. Tackle substantive comments in order of importance
5. Run any new analyses requested by reviewers
6. Revise the manuscript with tracked changes
7. Write the response letter point by point
8. Have a co-author review both the response and revised manuscript
9. Submit within the deadline (ask for extension if needed)
```
## Cover Letter for Resubmission
The cover letter to the editor should briefly summarize the major changes, highlight the most significant improvements, and note any disagreements with reviewers that you would like the editor to adjudicate. Keep it to one page. The detailed point-by-point responses belong in the separate response document, not the cover letter.Related Skills
thuthesis-guide
Write Tsinghua University theses using the ThuThesis LaTeX template
thesis-writing-guide
Templates, formatting rules, and strategies for thesis and dissertation writing
thesis-template-guide
Set up LaTeX templates for PhD and Master's thesis documents
sjtuthesis-guide
Write SJTU theses using the SJTUThesis LaTeX template with full compliance
novathesis-guide
LaTeX thesis template supporting multiple universities and formats
graphical-abstract-guide
Create SVG graphical abstracts for journal paper submissions
beamer-presentation-guide
Guide to creating academic presentations with LaTeX Beamer
plagiarism-detection-guide
Use plagiarism detection tools and ensure manuscript originality
paper-polish-guide
Review and polish LaTeX research papers for clarity and style
grammar-checker-guide
Use grammar and style checking tools to polish academic manuscripts
conciseness-editing-guide
Eliminate wordiness and redundancy in academic prose for clarity
ai-writing-humanizer
Remove AI-generated patterns to produce natural, authentic academic writing