# Jcr Rebuttal

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

- Skill: `thedixitjain/jcr-rebuttal` (Agent Skill)
- Install (CLI): `npx skillmds add thedixitjain/jcr-rebuttal`
- Raw SKILL.md: https://api.skillmd.com/api/skills/thedixitjain/jcr-rebuttal/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: thedixitjain (https://skillmd.com/u/thedixitjain)
- Updated: 2026-09-08
- Page: https://skillmd.com/skills/thedixitjain/jcr-rebuttal

---



# 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
```

---

**Source:** [`brycewang-stanford/Awesome-Journal-Skills`](https://github.com/brycewang-stanford/Awesome-Journal-Skills) → `Journal-of-Consumer-Research-Skills/skills/jcr-rebuttal/SKILL.md`