# Paper Review Response

> 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.

- Skill: `fengmo11/paper-review-response` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add fengmo11/paper-review-response`
- Raw SKILL.md: https://api.skillmd.com/api/skills/fengmo11/paper-review-response/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: fengmo11 (https://skillmd.com/u/fengmo11)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/fengmo11/paper-review-response

---


# 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

1. Assign stable IDs to every comment.
2. Classify each comment: method, result, writing, citation, figure, scope, ethics, or formatting.
3. Estimate risk: low, medium, high.
4. Map each comment to an action.
5. Draft the response in an editor-facing tone.
6. Link each promised change to a manuscript location.
7. Flag any missing author input or impossible request.
8. 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`.