jama-peer-review-revision
Use when responding to JAMA editor and reviewer comments after a revise decision, including the statistical-review queries. Structures the point-by-point response and revision; it does NOT fabricate new analyses or overstate changes.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jama-peer-review-revision --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Peer Review & Revision (jama-peer-review-revision) ## When to trigger - A decision letter arrives: major/minor revision (or a reject-with-encouragement) - Reviewer or editor comments need a structured, point-by-point reply - The statistical reviewer has raised analysis questions - You must revise the manuscript before writing the response — not after ## How JAMA review works (durable shape) - Editorial screening first; manuscripts that pass go to **external peer review**. - JAMA applies **dedicated statistical review** to manuscripts under serious consideration — expect detailed methods/analysis queries. - Decisions typically come with one or more revision rounds; address every point. ## Response-letter structure 1. **Open with thanks** and a one-paragraph summary of the main changes. 2. **Reproduce each comment verbatim**, then respond beneath it. 3. For each point: **state the change, quote the new manuscript text, and give the page/line**. If you disagree, do so respectfully with evidence — do not ignore a comment. 4. Group editor vs reviewer comments; number them (Reviewer 1, Comment 1.1 …). 5. Keep the manuscript and the letter perfectly consistent (numbers, claims, wording)
- When to trigger
- How JAMA review works (durable shape)
- Response-letter structure
- Handling common JAMA comment types
- Checklist
- Anti-patterns
- Operating pass for JAMA
- Output format
What does the jama-peer-review-revision skill do?
Use when responding to JAMA editor and reviewer comments after a revise decision, including the statistical-review queries. Structures the point-by-point response and revision; it does NOT fabricate new analyses or overstate changes.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill jama-peer-review-revision --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From brycewang-stanford/Awesome-Journal-Skills, a repository with 909 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.