icde-author-response
Use when responding to IEEE ICDE reviews, whether drafting a rebuttal to reviewer concerns or preparing a revise-and-resubmit change document for an invited ICDE revision under the 4-week window, coordinating with area chairs, addressing systems-reviewer pushback on baselines and cost, and deciding what is feasible before the revision deadline.
Profile →npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-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.
# ICDE Author Response Use this after ICDE reviews arrive. Reopen the current call's review-and-revision instructions before drafting, because ICDE's outcome model — and whether a Revise & Resubmit exists this edition — is edition-specific (待核实 for the current cycle). ## Two response genres ICDE can hand you either of two response tasks; identify which one you have before writing. 1. **A rebuttal** to initial reviews (where the process offers one) — a short, factual reply that corrects errors and answers the decision-critical objection per reviewer. 2. **A revise-and-resubmit change document** — when the first reviewing phase returns **Revise & Resubmit** (ICDE 2026 model), you get roughly **four weeks** to make concrete changes, re-reviewed by the same reviewers before a final Accept/Reject. ## Triage (both genres) - Answer concerns that affect correctness, novelty, evaluation soundness, or reproducibility first; cosmetic complaints last. - Because ICDE is **single-blind**, you may cite your own prior work and name your system freely — there is no anonymity to protect in the reply. - Anchor every answer to concrete evidence: a paper section, an added experiment, a disclosed cost,
- Two response genres
- Triage (both genres)
- The revision change document
- Systems-reviewer pushback patterns
- Feasibility discipline
- Output format
What does the icde-author-response skill do?
Use when responding to IEEE ICDE reviews, whether drafting a rebuttal to reviewer concerns or preparing a revise-and-resubmit change document for an invited ICDE revision under the 4-week window, coordinating with area chairs, addressing systems-reviewer pushback on baselines and cost, and deciding what is feasible before the revision deadline.
How do I install it?
Run `npx skills add brycewang-stanford/Awesome-Journal-Skills --skill icde-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 984 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.