joc-rebuttal
GitHub针对JoC R&R修订，在35页限制下协调多范式审稿人冲突。通过映射范式、分配资源（正文/附录/重构/拒绝）及公开处理分歧，规划修订策略与回复信，不伪造数据，确保论文连贯且符合匿名规范。
触发场景
安装
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill joc-rebuttal -g -y
SKILL.md
Frontmatter
{
"name": "joc-rebuttal",
"description": "Use when revising a Journal of Communication (JoC) manuscript after a revise-and-resubmit. The hard problem at JoC is that communication is a multi-paradigm field, so a single R&R can carry post-positivist, interpretive, critical, and computational reviewers who want incompatible things — inside a fixed 35-page cap. Plans the revision and response memo; it does not fabricate new results."
}
R&R Revision & Response (joc-rebuttal)
Communication is not a single-paradigm discipline, and JoC reviewers reflect that: one referee may reason as a post-positivist media-effects scholar, another as an interpretive or critical/cultural scholar, another from computational communication. A JoC R&R therefore is less "satisfy everyone" and more "broker across paradigms without breaking the paper" — and you must do it inside JoC's hard ~35-page limit (text, references, tables, figures, and endnotes all count). This skill is about that brokering and the page budget, not about inventing data.
When to trigger
- A JoC R&R arrived and you are scoping the revision before touching the manuscript
- Two reviewers want changes that come from different epistemologies and partly conflict
- Required additions threaten to push the paper over the 35-page cap
- You are writing the cover memo to the Editor-in-Chief
Step 1 — Map the reviewers by paradigm before you write anything
For each reviewer, label the stance their comments come from (post-positivist / interpretive / critical / computational / mixed) and what "convincing" means to them — more controls and robustness, richer interpretive warrant, sharper theoretical/critical stakes, or stronger validation and code. A demand that looks unreasonable usually makes sense once you name the paradigm behind it. The Editor-in-Chief's letter tells you which demands are load-bearing vs. optional.
Step 2 — Decide each comment with the page budget in view
Every comment resolves to one of four moves, and three of them cost pages:
| Move | When | Page-budget effect |
|---|---|---|
| Do in main text | load-bearing; the editor flagged it | costs pages — find offsets |
| Do in supplement | adds rigor but not the core argument | frees main-text pages (DAS/Appendix) |
| Reframe, don't add | the concern is about framing, not missing analysis | cheap; often the best move |
| Decline, with a reason | the request breaks the paper or comes from a paradigm the paper isn't written in | costs nothing; must be argued, not dodged |
When you add, say what you cut or moved to stay under 35 pages — reviewers and the editor see the tradeoff and trust it more than a paper that silently bloats.
Step 3 — Broker the cross-paradigm conflicts in the open
When a quantitative reviewer and an interpretive/critical reviewer pull opposite ways, do not quietly side with one. State the tension, choose a principled path that keeps the paper coherent in its own paradigm, and explain to the editor why that path serves the contribution. A paper that tries to be all paradigms at once usually loses its argument; defend what the study is.
Step 4 — Keep the revision submittable
- Double-anonymous integrity: the revised main document and supplements stay de-identified; keep self-citations in the third person.
- Transparency: update the Data Availability Statement and any Open Science Badge claims so
new analyses, data, or materials are covered (see
joc-open-science-and-transparency). - Format: still APA 7th, .docx, within ~35 pages; the JoC Forum reply path is for shorter exchanges, not full R&Rs.
Response memo structure (per reviewer, then a global note)
Lead with a short note to the editor: the 2–3 changes that matter most, and how you kept the paper under the page cap. Then, per reviewer, a compact entry:
R# (paradigm: post-positivist / interpretive / critical / computational)
• Comment → [paraphrase]
Action: did-in-text / did-in-supplement / reframed / declined(reason)
Where: §/p./Table/Fig./Supplement S# | Pages: +/- vs. prior draft
Anti-patterns
- Treating a different-paradigm comment as "wrong" instead of naming the stance and answering it on its terms
- Quietly satisfying one reviewer while ignoring a conflicting one
- Adding analyses until the paper busts the 35-page cap, with no statement of what moved
- Letting the Data Availability Statement / badges fall out of sync with the new analyses
- Re-identifying the authors in the revised file or supplements (breaks double-anonymity)
- Diluting the paper's own paradigm to look agreeable to every reviewer
Output format
【Reviewer paradigm map】R1/R2/R3 → stance + what "convincing" means to each
【Editor's load-bearing points】listed and solved first?
【Per-comment moves】in-text / supplement / reframe / decline — each with location
【Page budget】revised length ≤ ~35 pp; what was cut or moved to supplement
【Cross-paradigm conflicts】brokered in the open, paper's paradigm protected? [Y/N]
【Anonymity + DAS/badges】third-person self-cites + transparency updated? [Y/N]
【Next】resubmit via Manuscript Central
Supplementary resources
../../resources/official-source-map.md— review model, referee recommendations, page limit, and transparency policy
版本历史
- 1839142 当前 2026-07-05 13:29
