Use when writing the response to a Field Crops Research (FCR) revision decision (major or minor) and revising the manuscript. FCR reviewers commonly press on scope/generality, statistics and G×E, reproducibility detail, and a discussion that interprets rather than repeats. The response must address every point while protecting the contribution. Structures the response letter; it does not fabricate new results.
Scanned 6/5/2026
Install to Claude Code
npx -y skills add brycewang-stanford/Awesome-Journal-Skills --skill fcr-revision-and-rebuttal --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Fcr Revision And Rebuttal?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/brycewang-stanford-fcr-revision-and-rebuttal)More formats (shields.io, HTML) on the badges page.
---
name: fcr-revision-and-rebuttal
description: Use when writing the response to a Field Crops Research (FCR) revision decision (major or minor) and revising the manuscript. FCR reviewers commonly press on scope/generality, statistics and G×E, reproducibility detail, and a discussion that interprets rather than repeats. The response must address every point while protecting the contribution. Structures the response letter; it does not fabricate new results.
---
# Revision & Rebuttal (fcr-revision-and-rebuttal)
An FCR **revise** decision is an opportunity, not a formality. The response letter must move **every
reviewer** toward acceptance while keeping the editor confident the revision converges. FCR reviewers
tend to focus on a recurring set of agronomy concerns — answer them with **data and detail**, not
assertion.
## When to trigger
- A major- or minor-revision decision arrived and you are planning the response
- Reviewers disagree and you must reconcile their requests
- A reviewer wants additional environments, statistics, or reproducibility detail
- Writing the cover note to the editor summarising the revision
## Strategy
1. **Read the editor's letter as the rubric.** The editor signals the decisive points; solve those
first. The editor adjudicates disagreements among reviewers.
2. **Point-by-point, every comment addressed.** Quote each comment, then respond. Never skip one —
silence reads as non-compliance.
3. **Concede or rebut explicitly, with evidence.** For each: did what was asked (say where, with the
new text/table/figure number), or push back **respectfully with a reason** (design, agronomy, or
data). A well-argued disagreement beats a capitulation that weakens the paper.
4. **Reconcile conflicting reviewers openly.** When two reviewers want opposite things, say so, choose
a principled path, and explain the trade-off to the editor.
5. **Protect the contribution and scope.** Add analyses/robustness; resist changes that dilute the
general-relevance claim or over-fit to one environment.
## Common FCR reviewer asks (anticipate them)
| Reviewer concern | How to respond |
|------------------|----------------|
| "Generality / scope unclear" | restate multi-environment evidence; scope the claim explicitly |
| "Wrong/incomplete statistics" | refit with the correct mixed model / error structure; report SED/LSD, G×E |
| "Methods not reproducible" | add cultivar, soil, weather-vs-phenology, management, design detail |
| "Discussion repeats results" | rewrite to interpret and place in agronomic context |
| "Conclusions overreach" | add scope conditions; align conclusions to the data |
| "More seasons/sites needed" | add available environments or justify and bound the claim |
## Response-letter format
For each reviewer comment:
```
> [Quoted reviewer comment]
Response: [What we did / why we respectfully disagree].
Change: [Section/page/table-figure number where the revision appears].
```
Open with a short **summary of the main changes** to the editor; group by reviewer; end each entry
with the location of every change so the editor can verify quickly. Keep the data-availability
materials and exhibits in sync with any new analyses.
## Anti-patterns
- Ignoring or quietly merging away a comment without a visible response
- Capitulating to a request that breaks the agronomic logic just to please a reviewer
- Defensive or dismissive tone toward reviewers
- "We thank the reviewer" with no actual change or argued reason
- New analyses that drift out of sync with the deposited data or the exhibits
## Output format
```
【Editor's decisive points】addressed first? [list]
【Coverage】every reviewer comment answered? [Y/N]
【Concede vs rebut】each tagged with evidence + change location
【Reviewer conflicts】reconciled and explained to editor? [Y/N]
【Contribution/scope protected】no dilution of general relevance? [Y/N]
【Data/exhibits in sync】updated with new analyses? [Y/N]
【Next】resubmit via Editorial Manager
```
## Supplementary resources
- [`../../resources/external_tools.md`](../../resources/external_tools.md) — statistics packages for requested re-analyses
- [`../../resources/official-source-map.md`](../../resources/official-source-map.md) — review model and decision categories
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!