paper-writer
VerifiedMedical/scientific paper writing workflow skill. Manages the full pipeline from literature search to submission-ready manuscript. Creates and manages a project directory with IMRAD-format section files, literature matrix, reference management, and quality checklists. Supports both English and Japanese papers. Triggers: 'write paper', 'paper-write', 'start manuscript', '論文を書く', '論文執筆', '論文プロジェクト', 'manuscript', 'research paper', '原稿作成'.
templates/response-to-reviewers.md
View on GitHub# Response to Reviewers Template
## How to Use This Template
1. Copy this template for each revision round
2. Replace placeholders (marked with `[BRACKETS]`) with your content
3. Number every reviewer comment sequentially
4. Include specific page/line numbers for every change
5. Use the cover letter (separate template) for the editor; this document is the detailed point-by-point response
---
## Cover Page
**Manuscript ID:** [MANUSCRIPT-ID]
**Title:** [Full Manuscript Title]
**Journal:** [Journal Name]
**Revision Round:** [First Revision / Second Revision / etc.]
**Date:** [YYYY-MM-DD]
Dear Editor and Reviewers,
We sincerely thank you and the reviewers for the constructive feedback on our manuscript. We have carefully addressed all comments and believe the manuscript has been substantially improved. Below, we provide a detailed point-by-point response to each comment.
**Formatting convention used in this document:**
- **Reviewer comments** are shown in **bold**
- Our responses are in regular text
- Direct quotations from the revised manuscript are shown in > blockquotes
- New or modified text is highlighted with *italics* where applicable
---
## Reviewer 1
### General Comments
**Reviewer 1, General Comment:**
**[Paste the reviewer's general comment here verbatim]**
**Our Response:**
[Your response here. Thank the reviewer for their overall assessment. Address any broad concerns before moving to specific points.]
---
### Specific Comments
#### Comment 1.1
**Reviewer 1, Comment 1:**
**[Paste the specific comment here verbatim]**
**Our Response:**
[Your detailed response]
**Changes Made:**
[Description of what was changed, with specific locations]
- Page [X], Lines [Y-Z]: [Description of change]
- See revised manuscript, Section [X.X]
> [Quote the new/revised text from the manuscript]
---
#### Comment 1.2
**Reviewer 1, Comment 2:**
**[Paste the specific comment here verbatim]**
**Our Response:**
[Your detailed response]
**Changes Made:**
- Page [X], Lines [Y-Z]: [Description of change]
---
## Reviewer 2
### General Comments
**Reviewer 2, General Comment:**
**[Paste the reviewer's general comment here verbatim]**
**Our Response:**
[Your response]
---
### Specific Comments
#### Comment 2.1
**Reviewer 2, Comment 1:**
**[Paste the specific comment here verbatim]**
**Our Response:**
[Your detailed response]
**Changes Made:**
- Page [X], Lines [Y-Z]: [Description of change]
---
## Reviewer 3
*(Copy the same structure as above for each additional reviewer)*
---
## Summary of All Changes
| Section | Change Description | Triggered By |
|---------|-------------------|-------------|
| Abstract | [Brief description] | Reviewer 1, Comment 3 |
| Introduction | [Brief description] | Reviewer 2, Comment 1 |
| Methods | [Brief description] | Reviewer 1, Comment 5; Reviewer 3, Comment 2 |
| Results | [Brief description] | Reviewer 2, Comment 4 |
| Discussion | [Brief description] | Reviewer 1, Comment 7 |
| References | [Brief description] | Reviewer 3, Comment 6 |
| Supplementary | [Brief description] | Reviewer 2, Comment 8 |
---
## Best Practices for Responding to Reviewers
### Tone and Approach
1. **Always thank the reviewer** -- even for harsh or seemingly unfair comments. Every comment is an opportunity to strengthen your paper.
2. **Be respectful and professional.** Never be defensive, dismissive, or sarcastic.
3. **Be specific.** Vague responses like "We have revised the manuscript accordingly" are insufficient. State exactly what changed and where.
4. **Quote your revisions.** Show the reviewer the new text so they do not have to hunt for changes.
5. **Address every single point.** Do not skip or combine comments unless they are genuinely identical.
### Handling Different Comment Types
#### (a) Easy Fixes (Typos, Clarifications, Formatting)
**Strategy:** Fix immediately, respond briefly, show the change.
**Example:**
**Reviewer Comment:**
**"There is a typo in line 142: 'pateints' should be 'patients'."**
**Our Response:**
We thank the reviewer for catching this error. We have corrected the typo.
**Changes Made:**
- Page 6, Line 142: Corrected "pateints" to "patients"
---
#### (b) Disagreements with the Reviewer
**Strategy:** Acknowledge the reviewer's perspective, provide evidence-based reasoning for your position, offer a compromise if possible. Never say "the reviewer is wrong."
**Example:**
**Reviewer Comment:**
**"The authors should use a random forest model instead of logistic regression, as it would likely perform better."**
**Our Response:**
We appreciate the reviewer's suggestion regarding model selection. We chose logistic regression deliberately for the following reasons: (1) our primary goal was interpretability for clinical decision-making rather than maximal predictive performance (Smith et al., 2024); (2) our sample size (n=187) is relatively small, and logistic regression is more robust to overfitting in this setting (Hastie et al., 2009); and (3) the clinical guidelines in this domain require transparent, auditable models (FDA, 2023).
However, following the reviewer's suggestion, we have added a random forest comparison in the supplementary materials (Supplementary Table S3) to demonstrate that the performance difference is not clinically significant (AUC 0.82 vs. 0.84, p=0.31).
**Changes Made:**
- Page 12, Lines 267-270: Added justification for model selection
- Supplementary Table S3: Added random forest comparison results
---
#### (c) Requests for Additional Experiments/Analyses
**Strategy:** If feasible, do the analysis. If not feasible, explain why clearly and offer an alternative.
**Example (Feasible):**
**Reviewer Comment:**
**"The authors should perform a subgroup analysis by age group."**
**Our Response:**
We thank the reviewer for this excellent suggestion. We have performed the requested subgroup analysis, stratifying by age (<65 vs. ≥65 years). The results are presented in the new Table 3 and discussed in the Results section (Page 9, Lines 198-212).
**Example (Not Feasible):**
**Reviewer Comment:**
**"The authors should validate their model on an external dataset."**
**Our Response:**
We agree that external validation would strengthen the study. Unfortunately, no comparable external dataset with the required variables is currently available to our team. We have: (1) added internal validation using 5-fold cross-validation (new Table 4); (2) clearly stated this limitation in the Discussion (Page 14, Lines 312-318); and (3) identified external validation as a priority for future work. We are actively pursuing a collaboration with [Institution] to obtain an independent validation cohort.
---
#### (d) Conflicting Reviewer Opinions
**Strategy:** Acknowledge both perspectives transparently. Explain which approach you chose and why. Let the editor arbitrate if needed.
**Example:**
**Reviewer 1 Comment:**
**"The Discussion is too long and should be shortened."**
**Reviewer 3 Comment:**
**"The Discussion lacks depth and should explore more implications."**
**Our Response to Reviewer 1:**
We thank the reviewer for this feedback. We have streamlined the Discussion by removing redundant comparisons with prior literature (approximately 300 words removed). However, as Reviewer 3 requested additional depth on clinical implications, we have added a focused paragraph on implementation considerations (Page 15, Lines 340-355). The net result is a Discussion that is approximately 150 words shorter but more focused and substantive.
**Our Response to Reviewer 3:**
We appreciate this suggestion and have added a new paragraph discussing clinical implementation implications (Page 15, Lines 340-355). We have balanced this addition with streamlining other parts of the Discussion per Reviewer 1's feedback to maintain an appropriate length.
---
## Common Reviewer Comments and Example Responses
| Common Comment | Response Strategy |
|---------------|-------------------|
| "The sample size is too small" | Acknowledge limitation, provide power analysis, add to limitations section |
| "The literature review is incomplete" | Add missing references, explain your search strategy |
| "The statistical method is inappropriate" | Justify your choice with references, or add the suggested analysis |
| "The clinical significance is unclear" | Add effect sizes, NNT, or clinical context |
| "The writing needs improvement" | Have a native speaker review, or use professional editing service |
| "More details needed in Methods" | Add the requested details, refer to supplementary if space is limited |
| "The figures are unclear" | Redesign with higher resolution, clearer labels, and better color choices |
---
## 日本語セクション:査読者への回答テンプレート
### 基本フォーマット
**原稿番号:** [MANUSCRIPT-ID]
**タイトル:** [論文タイトル]
**雑誌名:** [雑誌名]
**改訂回:** [第1回改訂 / 第2回改訂]
**日付:** [YYYY年MM月DD日]
---
編集委員長・査読者の先生方
この度は、本原稿に対する丁寧かつ建設的なご査読を賜り、心より感謝申し上げます。いただいたすべてのご指摘に対して慎重に検討し、原稿を大幅に改善いたしました。以下に、各ご指摘への回答を項目ごとに記載いたします。
**本文書の表記規則:**
- **査読者のコメント**は**太字**で表記
- 著者の回答は通常書体で表記
- 改訂原稿からの引用は > ブロック引用で表記
---
### 査読者1
#### コメント1.1
**査読者1・コメント1:**
**[査読者のコメントをそのまま記載]**
**回答:**
[具体的な回答を記載]
**変更箇所:**
- [X]ページ、[Y-Z]行目:[変更内容の説明]
> [改訂後の本文を引用]
---
### 回答のポイント(日本語論文の場合)
1. **敬語を適切に使用する** -- 査読者は「先生」として扱う
2. **「ご指摘のとおり」から始める** -- 同意できる場合はまずそこから
3. **具体的なページ・行番号を必ず記載する**
4. **反論する場合も丁寧に** -- 「ご指摘は大変重要ですが、以下の理由により...」
5. **追加解析を行った場合は結果を明示する**
### よくある査読コメントへの回答例(日本語)
#### 症例数が少ないという指摘
**査読者コメント:**
**「症例数が少なく、結果の一般化可能性に疑問がある。」**
**回答:**
ご指摘いただきありがとうございます。本研究の症例数(n=XX)が比較的少数であることは認識しております。事前に行った検出力分析の結果、主要アウトカムに対して80%の検出力を達成するために必要な症例数はXX例であり、本研究はこの基準を満たしております([X]ページ、[Y]行目に追記)。一方で、症例数の限界についてはDiscussionのlimitationに明記いたしました([X]ページ、[Y-Z]行目)。
#### 統計手法への指摘
**査読者コメント:**
**「多重比較の補正が行われていない。」**
**回答:**
大変重要なご指摘をいただき感謝申し上げます。ご指摘に従い、Bonferroni補正を適用して再解析を行いました。補正後も主要な結果に変更はありませんでした(改訂版Table 2参照)。Methods([X]ページ、[Y]行目)およびResults([X]ページ、[Y]行目)を修正いたしました。
#### 臨床的意義への指摘
**査読者コメント:**
**「統計的有意差はあるが、臨床的意義が不明確である。」**
**回答:**
貴重なご指摘をいただきありがとうございます。臨床的意義を明確にするため、効果量(Cohen's d = X.XX)および治療必要数(NNT = XX)を追記いたしました([X]ページ、[Y-Z]行目)。また、Discussionにおいて、この結果が臨床現場でどのような意味を持つかについて具体的に記述を追加いたしました([X]ページ、[Y-Z]行目)。
---
## Checklist Before Submitting Response
- [ ] Every reviewer comment has been addressed individually
- [ ] All responses include specific page and line numbers
- [ ] Revised text is quoted where appropriate
- [ ] Tone is respectful and professional throughout
- [ ] Summary table of changes is complete
- [ ] Cover letter (separate document) references this response
- [ ] Co-authors have reviewed and approved the response
- [ ] Track changes are enabled in the revised manuscript
- [ ] Supplementary materials are updated if applicable
- [ ] Response document is formatted per journal requirements
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |