icse-author-response
Use when drafting an ICSE author response or executing a Major Revision, covering criterion-targeted replies to research-track reviews, the September response window, the four-week revision sprint to the November deadline, response-letter structure, and change tracking that survives PC re-review.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-author-response --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.
# ICSE Author Response ICSE gives authors two distinct speaking turns, and they demand different documents. The **author response** (September in the 2027 cycle, checked 2026-07-08) answers reviews before first decisions; the **Major Revision response letter** (revision due November 17, 2026; final decision December 18) accompanies a changed paper re-read by the same reviewers. Do not write the first as if it were the second. ## Turn 1: the author response You are writing for the PC discussion, not for your own catharsis. Three moves earn their space: 1. **Correct factual misreadings**, with a page/section pointer: "R2 states we evaluate on toy programs; §5.1 lists the 17 real-world projects (median 210 kLOC)." 2. **Supply requested evidence that already exists** — a number, a table cell, a clarification of the study protocol. If it fits in a sentence, give the sentence, not a promise. 3. **Commit to feasible changes**, scoped to what a Major Revision window can hold. "We will add effect sizes to Table 4" is credible; "we will run a controlled experiment with professional developers" is not. Map every reply to the criterion it defends. ICSE reviews are structured around novelty, ri
- Turn 1: the author response
- Turn 2: the Major Revision
- Revision-sprint triage
- Tone calibration
- Anti-patterns
- Output format
What does the icse-author-response skill do?
Use when drafting an ICSE author response or executing a Major Revision, covering criterion-targeted replies to research-track reviews, the September response window, the four-week revision sprint to the November deadline, response-letter structure, and change tracking that survives PC re-review.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icse-author-response --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.