| name | paper-review-response |
| description | Use when drafting, auditing, or structuring reviewer responses, rebuttal letters, revision maps, comment IDs, response-to-reviewer tables, manuscript change tracking, and polite evidence-forward disagreement. |
Paper Review Response
Use this skill when responding to reviewer or editor comments. The goal is to create a traceable, polite, evidence-forward revision package.
Inputs
- Decision letter and reviewer comments.
- Revised manuscript or planned changes.
- Page/line/section locations if available.
- Constraints: time, data, experiments, journal rules.
Workflow
- Assign stable IDs to every comment.
- Classify each comment: method, result, writing, citation, figure, scope, ethics, or formatting.
- Estimate risk: low, medium, high.
- Map each comment to an action.
- Draft the response in an editor-facing tone.
- Link each promised change to a manuscript location.
- Flag any missing author input or impossible request.
- Produce a response map and final response letter.
Response Gate
- No reviewer comment is skipped.
- No experiment, citation, figure, line number, or manuscript change is invented.
- Disagreements are respectful and evidence-forward.
- All claimed changes have locations.
- Remaining limitations are acknowledged rather than hidden.
When To Read References
- For action codes and tone patterns, read
references/response-patterns.md.
- For output format, use
../../templates/reviewer-response-map.md.
