Review Response
A systematic review response workflow that helps researchers efficiently and professionally reply to reviewer comments.
Core Features
- Review Analysis - Parse and classify reviewer comments (Major/Minor/Typo/Misunderstanding)
- Response Strategy - Develop response strategies for different comment types (Accept/Defend/Clarify/Experiment)
- Rebuttal Writing - Write structured, professional rebuttal documents
- Tone Management - Optimize tone to maintain professionalism, respect, and evidence-based arguments
Workflow
Receive reviewer comments -> Parse and classify -> Develop strategy -> Write responses -> Tone check -> Final rebuttal
When to Use
Use this skill when you need to:
- "Help me write a rebuttal"
- "How to respond to reviewer comments"
- "Analyze these review comments"
- "Develop a review response strategy"
Usage Steps
- Provide reviewer comments - Share the reviewer comments text or file with Claude
- Analysis and classification - Claude automatically parses and classifies the comments
- Strategy recommendations - Receive response strategy suggestions for each comment
- Write rebuttal - Generate a structured rebuttal document based on the strategy
- Optimize tone - Review and optimize the professionalism and politeness of responses
Core Principles
- Professionalism - Maintain an academically professional tone and expression
- Respectfulness - Respect the reviewers' opinions and time
- Evidence-based - Support every response with sufficient reasoning and evidence
- Completeness - Ensure all reviewer comments receive a response
Success Factors (Based on ICLR Spotlight Paper Analysis)
Key lessons extracted from successful rebuttal cases:
1. Acknowledge Strengths, Respond Positively to Criticism
- Reviewers will first acknowledge the paper's strengths (novelty, impact, practical applicability)
- Even spotlight papers receive constructive criticism
- Strategy: Thank reviewers for acknowledged strengths first, then address criticism specifically
2. Provide Clarity and Intuitive Understanding
- Even high-quality papers may have clarity issues
- Need to provide intuition and detailed explanations for readers with different backgrounds
- Strategy: Expand key sections, move technical details to appendix, add step-by-step walkthroughs
3. Thorough Justification of Experimental Setup
- Need to justify experimental setup choices
- Consider and discuss alternative metrics
- Provide comprehensive experiments to support claims
- Strategy: Add ablation studies, explain why specific experimental setups were chosen
4. Emphasis on Ethical Considerations
- For research involving privacy, security, and other sensitive topics, ethical considerations are crucial
- Reviewers pay special attention to ethical implications
- Strategy: Proactively discuss ethical considerations, even if reviewers don't explicitly request it
5. Highlight Practical Application Value
- Reviewers value practical applicability and scalability of methods
- "Easily applicable" and "scalable" are important strengths
- Strategy: Emphasize practical benefits and scalability in the rebuttal
Integration with active installed writing memory
When the rebuttal task involves:
- tone calibration,
- rebuttal phrasing,
- clarification language,
- structuring multi-point responses,
- or learning from strong prior paper/review writing,
read the active installed writing memory before drafting:
~/.claude/skills/ml-paper-writing/references/knowledge/paper-miner-writing-memory.md on Claude Code installs
- the equivalent installed skill-home path on Codex/OpenCode branches
- otherwise skip this optional memory and continue with the local review-response references
Default read order for rebuttal work
- reviewer comments and paper context
- optional
paper-miner-writing-memory.md if available
references/response-strategies.md
references/rebuttal-templates.md
references/tone-guidelines.md
Read narrowly:
- start with
How this helps our writing,
- then inspect
Reusable phrasing,
- then inspect
Venue-specific signals if the rebuttal is venue-sensitive,
- use
Writing patterns mined only when the response needs stronger rhetorical structure.
Do not quote the memory mechanically. Use it to improve structure, clarity, restraint, and professionalism.
Evidence anchor rule
Every response row must include one of:
- paper location,
- result table / figure / analysis artifact,
- citation / Evidence Record ID,
- planned experiment with status,
unresolved if no evidence exists yet.
Do not claim "we added experiments" or "the results show" without naming the artifact. If an objection has multiple atomic points, split it and cover each point separately.
Reference Documents
For detailed guides, refer to:
references/review-classification.md - Review comment classification criteria
references/response-strategies.md - Response strategy library
references/rebuttal-templates.md - Rebuttal templates and examples
references/tone-guidelines.md - Tone and expression guidelines
Related Tools
- Agent:
rebuttal-writer - Dedicated agent for rebuttal writing and optimization
- Command:
/rebuttal <review_file> - Quick-start the rebuttal workflow
1---
2name: review-response
3description: Systematic review response workflow from comment analysis to professional rebuttal writing. Use when the user asks to "write rebuttal", "respond to reviewers", "draft review response", or "analyze review comments". Improves paper acceptance rates.
4tags: [Research, Academic, Rebuttal, Paper Writing]
5version: 0.1.0
6metadata:
7 source: https://skillmd.com/skills/galaxy-dawn/review-response
8---
9
10# Review Response
11
12A systematic review response workflow that helps researchers efficiently and professionally reply to reviewer comments.
13
14## Core Features
15
161. **Review Analysis** - Parse and classify reviewer comments (Major/Minor/Typo/Misunderstanding)
172. **Response Strategy** - Develop response strategies for different comment types (Accept/Defend/Clarify/Experiment)
183. **Rebuttal Writing** - Write structured, professional rebuttal documents
194. **Tone Management** - Optimize tone to maintain professionalism, respect, and evidence-based arguments
20
21## Workflow
22
23```
24Receive reviewer comments -> Parse and classify -> Develop strategy -> Write responses -> Tone check -> Final rebuttal
25```
26
27## When to Use
28
29Use this skill when you need to:
30- "Help me write a rebuttal"
31- "How to respond to reviewer comments"
32- "Analyze these review comments"
33- "Develop a review response strategy"
34
35## Usage Steps
36
371. **Provide reviewer comments** - Share the reviewer comments text or file with Claude
382. **Analysis and classification** - Claude automatically parses and classifies the comments
393. **Strategy recommendations** - Receive response strategy suggestions for each comment
404. **Write rebuttal** - Generate a structured rebuttal document based on the strategy
415. **Optimize tone** - Review and optimize the professionalism and politeness of responses
42
43## Core Principles
44
45- **Professionalism** - Maintain an academically professional tone and expression
46- **Respectfulness** - Respect the reviewers' opinions and time
47- **Evidence-based** - Support every response with sufficient reasoning and evidence
48- **Completeness** - Ensure all reviewer comments receive a response
49
50## Success Factors (Based on ICLR Spotlight Paper Analysis)
51
52Key lessons extracted from successful rebuttal cases:
53
54### 1. Acknowledge Strengths, Respond Positively to Criticism
55- Reviewers will first acknowledge the paper's strengths (novelty, impact, practical applicability)
56- Even spotlight papers receive constructive criticism
57- **Strategy**: Thank reviewers for acknowledged strengths first, then address criticism specifically
58
59### 2. Provide Clarity and Intuitive Understanding
60- Even high-quality papers may have clarity issues
61- Need to provide intuition and detailed explanations for readers with different backgrounds
62- **Strategy**: Expand key sections, move technical details to appendix, add step-by-step walkthroughs
63
64### 3. Thorough Justification of Experimental Setup
65- Need to justify experimental setup choices
66- Consider and discuss alternative metrics
67- Provide comprehensive experiments to support claims
68- **Strategy**: Add ablation studies, explain why specific experimental setups were chosen
69
70### 4. Emphasis on Ethical Considerations
71- For research involving privacy, security, and other sensitive topics, ethical considerations are crucial
72- Reviewers pay special attention to ethical implications
73- **Strategy**: Proactively discuss ethical considerations, even if reviewers don't explicitly request it
74
75### 5. Highlight Practical Application Value
76- Reviewers value practical applicability and scalability of methods
77- "Easily applicable" and "scalable" are important strengths
78- **Strategy**: Emphasize practical benefits and scalability in the rebuttal
79
80## Integration with active installed writing memory
81
82When the rebuttal task involves:
83- tone calibration,
84- rebuttal phrasing,
85- clarification language,
86- structuring multi-point responses,
87- or learning from strong prior paper/review writing,
88
89read the active installed writing memory before drafting:
90
91- `~/.claude/skills/ml-paper-writing/references/knowledge/paper-miner-writing-memory.md` on Claude Code installs
92- the equivalent installed skill-home path on Codex/OpenCode branches
93- otherwise skip this optional memory and continue with the local review-response references
94
95### Default read order for rebuttal work
96
971. reviewer comments and paper context
982. optional `paper-miner-writing-memory.md` if available
993. `references/response-strategies.md`
1004. `references/rebuttal-templates.md`
1015. `references/tone-guidelines.md`
102
103Read narrowly:
104- start with `How this helps our writing`,
105- then inspect `Reusable phrasing`,
106- then inspect `Venue-specific signals` if the rebuttal is venue-sensitive,
107- use `Writing patterns mined` only when the response needs stronger rhetorical structure.
108
109Do not quote the memory mechanically. Use it to improve structure, clarity, restraint, and professionalism.
110
111## Evidence anchor rule
112
113Every response row must include one of:
114- paper location,
115- result table / figure / analysis artifact,
116- citation / Evidence Record ID,
117- planned experiment with status,
118- `unresolved` if no evidence exists yet.
119
120Do not claim "we added experiments" or "the results show" without naming the artifact. If an objection has multiple atomic points, split it and cover each point separately.
121
122## Reference Documents
123
124For detailed guides, refer to:
125- `references/review-classification.md` - Review comment classification criteria
126- `references/response-strategies.md` - Response strategy library
127- `references/rebuttal-templates.md` - Rebuttal templates and examples
128- `references/tone-guidelines.md` - Tone and expression guidelines
129
130## Related Tools
131
132- **Agent**: `rebuttal-writer` - Dedicated agent for rebuttal writing and optimization
133- **Command**: `/rebuttal <review_file>` - Quick-start the rebuttal workflow