jcp-rebuttal
GitHub专为JCP修改重投(R&R)设计的反驳信撰写技能。核心策略是以新实证证据(如操纵中介实验)回应审稿人关切,而非单纯辩论。提供结构化写作指南、常见需求应对表及异议处理技巧,旨在将批评转化为机制验证,提升录用率。
触发场景
安装
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jcp-rebuttal -g -y
SKILL.md
Frontmatter
{
"name": "jcp-rebuttal",
"description": "Use when drafting the response letter and revision for a Journal of Consumer Psychology (JCP) R&R — turning reviewer process concerns into new studies, writing the point-by-point response, and showing the mechanism is now nailed. Drafts the rebuttal; for reading the letter and feasibility see jcp-review-process."
}
Rebuttal Strategy (jcp-rebuttal)
When to trigger
- You have a JCP major revision and must write the response letter and revise
- A reviewer demands a mechanism study and you need to convert that into a concrete design + response
- You disagree with a reviewer but must push back without antagonizing the editor
- The revision adds studies and you need to show the process claim is now established
- You are unsure how to structure a point-by-point response for a multi-reviewer letter
The JCP rebuttal is mostly new evidence, not argument
At a process journal, you rarely win an R&R by argument alone. The strongest JCP responses to "the mechanism isn't established" run the study the reviewer implies — a manipulated-mediator or moderation-of-process experiment that turns the effect off when the process is blocked — and then say, plainly, "We agree this was a gap; Study 4 now demonstrates the process directly." Reviewers in the SCP community respond well to authors who treat the critique as a chance to strengthen the mechanism rather than to defend the original draft. Lead with what you did, not with why the reviewer is wrong.
Structuring the response letter
- Open with a synthesis: a short paragraph naming the editor's binding concern and how the revision addresses it (new studies, ruled-out alternatives, higher power).
- Point-by-point, verbatim: quote each comment, then respond. State the change, point to the manuscript page/study, and quote the new text where useful.
- Group by theme where reviewers overlap (the common "mechanism unclear" thread) so you answer the real issue once and reference it.
- Show, don't assert: report the new study's result (effect size + CI) in the letter, not just "we added a study."
- Be concise and respectful: the editor re-reads this; a defensive or sprawling letter hurts you.
Handling the recurring JCP demands
| Reviewer demand | Winning response |
|---|---|
| "Effect in search of a process" | Add a manipulated-mediator / moderation-of-process study; report it as the new centerpiece |
| "Alternative explanation X" | Add a study whose moderation your process predicts but X does not; or measure and rule out X |
| "Underpowered / not pre-registered" | Pre-register and replicate the key study at adequate power; report the OSF link |
| "Stimulus-bound" | Add a study with a new operationalization/population or a consequential behavioral DV |
| "Measured mediation is weak" | Upgrade to experimental mediation; reframe the original as supporting, not dispositive |
When you must disagree
- Disagree with evidence, not assertion: a new analysis, a citation, or a study that addresses the underlying worry.
- Acknowledge the reviewer's logic before explaining why the data point the other way.
- If a request would damage the paper (e.g., a study that tests a different theory), explain the conceptual reason and offer an alternative that addresses the spirit of the comment.
- Never go over the editor's head on a point the editor endorsed; align with the editor's letter.
Checklist
- The letter opens with the editor's binding concern and how the revision resolves it
- Every comment is quoted and answered point-by-point, with manuscript locations
- The "mechanism unclear" thread is answered with a new process study, results reported in the letter
- Alternative explanations are ruled out by design/data, not just argued away
- New confirmatory studies are pre-registered; links provided
- Disagreements are evidence-backed and aligned with the editor's framing
- Tone is concise, professional, and non-defensive throughout
Anti-patterns
- Argue-don't-run: rebutting a "need a mechanism study" comment with prose and reanalysis only
- Defensive letter: reasserting the original draft instead of strengthening the process
- Buried results: "we added Study 4" without reporting what it showed
- Reviewer whack-a-mole: answering each comment in isolation while missing the shared concern
- Editor end-run: fighting a point the editor's letter endorsed
- Over-promise gap: claiming a study addresses a concern it does not actually test
Output format
【Editor's binding concern】restated in one line
【New studies added】which, and the result (effect size + CI) reported in the letter
【Mechanism now established by】the manipulated-mediator / moderation-of-process study
【Alternatives ruled out】how (design/data)
【Disagreements】where, with what evidence, aligned with editor
【Tone check】concise, respectful, non-defensive? [Y/N]
【Next step】resubmit via ScholarOne; if reject, jcp-review-process to reroute
版本历史
- 1839142 当前 2026-07-05 13:29


