jcr-rebuttal

GitHub

针对JCR修改重投(R&R)的修订与反驳指南。涵盖修订计划制定、新增研究设计、满足强制透明度要求(数据/代码归档),以及撰写逐点回复信。强调先实质性修订再写作,遵循编辑优先级,高效解决审稿人关切。

Journal-of-Consumer-Research-Skills/skills/jcr-rebuttal/SKILL.md brycewang-stanford/Awesome-Journal-Skills

Trigger Scenarios

收到JCR修改重投通知并需制定修订及回复计划 审稿人要求补充实验、过程证据或数据分析 需在邀请修订阶段满足数据材料公开和透明性要求 需要协调不同学科审稿人的冲突意见

Install

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jcr-rebuttal -g -y
More Options

Non-standard path

npx skills add https://github.com/brycewang-stanford/Awesome-Journal-Skills/tree/main/Journal-of-Consumer-Research-Skills/skills/jcr-rebuttal -g -y

Use without installing

npx skills use brycewang-stanford/Awesome-Journal-Skills@jcr-rebuttal

指定 Agent (Claude Code)

npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jcr-rebuttal -a claude-code -g -y

安装 repo 全部 skill

npx skills add brycewang-stanford/Awesome-Journal-Skills --all -g -y

预览 repo 内 skill

npx skills add brycewang-stanford/Awesome-Journal-Skills --list

SKILL.md

Frontmatter
{
    "name": "jcr-rebuttal",
    "description": "Use when responding to a Journal of Consumer Research (JCR) revise-and-resubmit — planning the revision, running new studies or analyses, satisfying the transparency requirements that become mandatory at invited revision, and drafting a point-by-point response letter for double-anonymized re-review. Drafts the response after the revision is real; it does not interpret the decision (jcr-review-process)."
}

Revision & Rebuttal (jcr-rebuttal)

When to trigger

  • You received a JCR R&R and need a plan plus a response letter
  • Reviewers want additional studies, process evidence, or analyses
  • You must satisfy data/materials posting now required at invited revision
  • You are reconciling conflicting reviewer requests across disciplines

Revise first, write the letter second

A JCR response letter documents revisions that already exist. Sequence the work:

  1. Triage by the editor's priorities. The co-editor's letter signals which concerns are decisive — fix those substantively, not cosmetically.
  2. Strengthen the conceptual contribution. If reviewers found it incremental, sharpen the advance/deepen/repudiate claim (jcr-contribution-framing) — re-running studies will not save a thin contribution.
  3. Add the evidence the genre demands. Experiments: new studies for process (manipulated mediator, predicted moderators), replications across stimuli/populations, cleaner inference (jcr-data-analysis). CCT: deeper grounding, additional informants, a tighter audit trail.
  4. Reconcile conflicts transparently. Where reviewers disagree, choose a defensible path, explain the reasoning, and let the editor adjudicate — do not silently split the difference.

Satisfy the transparency requirements that activate at revision

At invited revision, JCR's transparency regime tightens: posting of data and study materials to an approved repository (OSF, Harvard Dataverse, Qualitative Data Repository, ResearchBox) becomes required (accessible to editors) unless an exemption is granted, and replication code must be provided. Update the Data Collection Statement to cover any new studies. Confirm your data-retention plan (≥ 7 years). Address any transparency reviewer concerns explicitly in the letter.

New-study economy

Do not answer every concern with another study. Use this triage:

Reviewer concern Strong response Weak response
Mechanism/process unclear A targeted mediator, moderator, process measure, or qualitative trace that discriminates the proposed mechanism from rivals A broad extra study that repeats the main effect
Generalizability challenged A sample, stimulus, context, or cultural setting that tests the stated boundary A convenience replication with no new boundary information
CCT grounding challenged More field evidence, negative cases, informant variation, or audit-trail clarity Extra quotation volume without interpretive leverage
Transparency challenged Repository deposit, code, materials, and a revised Data Collection Statement A promise that materials will be available later

Cap the revision plan at the smallest set of changes that resolves the editor's decisive doubts. If a new study does not change the conceptual conclusion, use a robustness appendix or drop it.

Writing the point-by-point response

  • Open with a brief summary of the major changes and gratitude for the developmental feedback.
  • Address every comment in order, per reviewer: quote the comment, state what you changed, and point to the manuscript location (page/section, new study number, new exhibit).
  • Show, don't assert. Reference new results, new figures, and repository links rather than promising compliance.
  • Keep anonymization intact. The revised manuscript re-enters double-anonymized review — re-scrub identifiers, keep self-citations neutral, describe field sites generically.
  • Respect the page cap. New studies must fit the 60-page manuscript (embedded exhibits count); push supporting material to the web appendix (≤ 40 MB).

Checklist

  • Editor's decisive concerns addressed substantively
  • Contribution sharpened if flagged as incremental
  • New process evidence / replications (experiments) or deeper grounding (CCT) added
  • Conflicting reviewer requests reconciled with transparent reasoning
  • Data/materials posted to an approved repository; replication code supplied; Data Collection Statement updated
  • New-study economy checked: each new study resolves a specific decisive doubt
  • Point-by-point letter quotes each comment and cites manuscript locations
  • Revised manuscript re-anonymized; within 60 pages; overflow in the web appendix

Anti-patterns

  • Promising changes in the letter that the manuscript does not contain.
  • Cosmetic edits to decisive concerns.
  • Adding studies that bloat the manuscript past the page cap.
  • Ignoring transparency requirements that become mandatory at revision.
  • Breaking anonymization when describing new data or sites.
  • Treating every reviewer request as a demand for a full new study, then losing the conceptual thread.

Output format

【Editor's priorities】addressed: [...]
【Contribution】sharpened? advance/deepen/repudiate restated
【New evidence】studies/analyses (experiments) or grounding (CCT) added
【Conflicts】reconciled with reasoning
【Transparency】repository deposit + code + updated Data Collection Statement: done?
【Response letter】point-by-point, with locations; re-anonymized; ≤60 pp
【Next step】resubmit via ScholarOne → jcr-review-process

Version History

  • 1839142 Current 2026-07-05 13:30

Same Skill Collection

AAAI-Skills/skills/aaai-artifact-evaluation/SKILL.md
AAAI-Skills/skills/aaai-author-response/SKILL.md
AAAI-Skills/skills/aaai-camera-ready/SKILL.md
AAAI-Skills/skills/aaai-experiments/SKILL.md
AAAI-Skills/skills/aaai-related-work/SKILL.md
AAAI-Skills/skills/aaai-reproducibility/SKILL.md
AAAI-Skills/skills/aaai-review-process/SKILL.md
AAAI-Skills/skills/aaai-submission/SKILL.md
AAAI-Skills/skills/aaai-supplementary/SKILL.md
AAAI-Skills/skills/aaai-topic-selection/SKILL.md
AAAI-Skills/skills/aaai-workflow/SKILL.md
AAAI-Skills/skills/aaai-writing-style/SKILL.md
AAMAS-Skills/skills/aamas-artifact-evaluation/SKILL.md
AAMAS-Skills/skills/aamas-author-response/SKILL.md
AAMAS-Skills/skills/aamas-camera-ready/SKILL.md
AAMAS-Skills/skills/aamas-experiments/SKILL.md
AAMAS-Skills/skills/aamas-related-work/SKILL.md
AAMAS-Skills/skills/aamas-reproducibility/SKILL.md
AAMAS-Skills/skills/aamas-review-process/SKILL.md
AAMAS-Skills/skills/aamas-submission/SKILL.md
AAMAS-Skills/skills/aamas-supplementary/SKILL.md
AAMAS-Skills/skills/aamas-topic-selection/SKILL.md
AAMAS-Skills/skills/aamas-workflow/SKILL.md
AAMAS-Skills/skills/aamas-writing-style/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-editor-strategy/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-evidence-standards/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-literature-synthesis/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-organizing-framework/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-proposal-framing/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-review-process/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-revision/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-submission/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-tables-figures/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-topic-selection/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-workflow/SKILL.md
Academy-of-Management-Annals-Skills/skills/amann-writing-style/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-contribution-framing/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-data-analysis/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-literature-positioning/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-methods/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-rebuttal/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-review-process/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-submission/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-tables-figures/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-theory-development/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-topic-selection/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-workflow/SKILL.md
Academy-of-Management-Journal-Skills/skills/amj-writing-style/SKILL.md
Academy-of-Management-Review-Skills/skills/amr-contribution-framing/SKILL.md
Academy-of-Management-Review-Skills/skills/amr-data-analysis/SKILL.md

Metadata

Files
0
Version
9f86f09
Hash
ce2cd076
Indexed
2026-07-05 13:30

Accueil - Wiki
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-30 07:00
浙ICP备14020137号-1 $Carte des visiteurs$