Agent Skills
› brycewang-stanford/Awesome-Journal-Skills
› psychrev-rebuttal
psychrev-rebuttal
GitHub用于处理《心理评论》大修决定后的回复信撰写与理论修订。通过分类审稿意见，指导用户先修改理论再撰写逐点回复，强调实质性改进、明确引用位置及有节制的反驳，避免空洞辩护。
Trigger Scenarios
收到大修或小修决定
需针对审稿意见撰写逐点回复
面临理论修订而非单纯文字润色
Install
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill psychrev-rebuttal -g -y
SKILL.md
Frontmatter
{
"name": "psychrev-rebuttal",
"description": "Use when a Psychological Review decision letter (usually a major revision) has arrived and you must write the response document and revise the theory. Drafts the response and revision plan; it does NOT run the resubmission preflight (psychrev-submission) or build new theory from scratch (psychrev-theory-construction)."
}
Revision & Response Document (psychrev-rebuttal)
Write the response after the theory has actually been revised. At a theory journal a response that argues rather than strengthens the model fails. Revise first, then document.
When to trigger
- A major/minor revision decision has arrived
- You have reviewer comments and must produce a point-by-point response
- You are tempted to defend the model rather than improve it
- You must decide which asks change the theory and which are presentation
Read the letter for the theory, not the edits
Reviewers at Psychological Review are usually proponents or critics of the rival models. Their comments encode theoretical demands beneath the surface wording. Before drafting, classify every comment:
| Comment encodes... | Response strategy |
|---|---|
| "Your model is the same as [rival]" | Sharpen subsumption/differentiation; show the limiting case (psychrev-contribution-framing) |
| "How do you know this prediction follows?" | Add/strengthen the derivation (psychrev-argument-development) |
| "Couldn't a simpler account do this?" | Add the head-to-head on a diagnostic phenomenon |
| "Is this parameter identifiable?" | Add parameter-recovery simulation (psychrev-boundary-conditions) |
| "The model explains too much" | State scope and a breakdown regime |
| "What would falsify it?" | Add a risky novel prediction |
| "This reads as empirical / out of scope" | Reframe so data only constrain; re-establish fit |
Building the response document
- Open with the substantive changes, not gratitude boilerplate: a short paragraph naming the two or three ways the theory is now stronger (new derivation, identifiability analysis, scope statement, head-to-head comparison).
- Point-by-point, quoting each comment, then: what you changed, where (section/figure/eq. number), and — only where you genuinely disagree — a respectful, evidence-based rebuttal.
- Show the theory changed. For a theory journal, "we clarified the wording" rarely suffices when the comment was about the model; point to the new derivation, simulation, or scope statement.
- Concede on your own terms. Where a reviewer is right that the model cannot do Y, fold Y into the boundary conditions as a stated limit rather than over-reaching to cover it.
- Disagree carefully. You may push back on a rival-modeler reviewer, but only with a derivation or a diagnostic comparison — never with assertion. Make the editor's adjudication easy.
Tone and discipline
- Respectful, specific, and concrete — every claim of "we revised" carries a location.
- Never dismissive of the rival models the reviewers represent.
- Track changes / a clearly marked revised manuscript accompanies the response (per portal).
- If two reviewers conflict, surface the conflict for the editor and state your principled choice.
Checklist
- Every reviewer comment addressed point-by-point, quoted, with a located change
- Each theoretical ask answered with a theory change (derivation/simulation/scope), not just wording
- Disagreements backed by derivation or diagnostic comparison, never bare assertion
- Concessions folded into boundary conditions rather than over-reaching
- Conflicting reviewer demands surfaced for the editor with a principled resolution
- A summary of the main strengthening opens the document
- Revised manuscript marked (track changes) and consistent with the response
Anti-patterns
- Arguing the model is fine instead of strengthening it (fatal at a theory journal)
- "We thank the reviewer" boilerplate with no located change
- Defending against a rival-modeler reviewer by assertion rather than derivation
- Over-reaching to cover a phenomenon a reviewer rightly flagged, instead of bounding it
- Cosmetic edits in response to a substantive theoretical objection
- Ignoring a reviewer conflict and hoping the editor does not notice
Output format
【Summary of strengthening】[2–3 ways the theory is now stronger]
【Point-by-point】[comment → change made → location | or reasoned rebuttal with derivation]
【Theory changes】[new derivations / simulations / scope statements added]
【Concessions】[phenomena now bounded out, on our terms]
【Editor notes】[any reviewer conflicts surfaced + principled choice]
【Next step】psychrev-submission (resubmission preflight)
Version History
- 1839142 Current 2026-07-05 14:15
