paper-revision
Revise papers based on reviewer feedback. Map reviewer concerns to specific sections, apply targeted edits, run additional experiments if needed, and verify improvements. Use after receiving peer review with revision requests.
Install
npx skills add https://github.com/lingzhi227/agent-research-skills --skill paper-revisionSKILL.md
Paper Revision
Systematically revise papers based on reviewer feedback.
Input
$0— Reviewer comments/feedback$1— Current paper draft (main.tex or paper directory)
References
- Revision workflow and prompts:
~/.claude/skills/paper-revision/references/revision-prompts.md
Workflow
Step 1: Parse and Prioritize Concerns
For each reviewer comment:
- Extract the specific concern
- Classify: major revision, minor revision, question, suggestion
- Map to affected paper section(s)
- Prioritize: address major concerns first
Step 2: Plan Revisions
Create a revision plan:
Concern → Affected Section → Required Action → New Content/Experiment
Categories of actions:
- Clarification: Rewrite text for clarity
- Additional experiment: Run new experiment, add results
- New analysis: Add ablation, statistical test, or comparison
- Structural change: Move, merge, or split sections
- Citation: Add missing references
Step 3: Execute Revisions
For each planned revision:
- Read the current section
- Apply targeted edits (preserve surrounding structure)
- If new experiments needed: use experiment-code skill
- If new figures/tables needed: use figure-generation / table-generation skills
- Mark changes (use
\textcolor{blue}{...}for revised text)
Step 4: Verify Improvements
- Re-run self-review skill to check if scores improved
- Verify all reviewer concerns are addressed
- Check that revisions don't introduce new issues
- Ensure page count still fits venue requirements
Step 5: Write Revision Summary
Generate a diff summary:
- List all changes made with section references
- Note any new experiments, figures, or tables added
- Cross-reference each change to the reviewer concern it addresses
Rules
- Address EVERY reviewer concern — do not skip any
- Preserve paper structure unless structural change is explicitly needed
- New results must come from actual experiments, not hallucinated
- Mark all revised text clearly for the reviewers
- Keep a copy of the previous version before revising
- Compare new scores vs previous scores after revision
Related Skills
- Upstream: self-review
- Downstream: paper-compilation
- See also: rebuttal-writing, paper-writing-section
Related skills
researchmattpocock575KInvestigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.paper-context-resolverlllllllama451KRigor Paper Context helper for README-first deep learning repo reproduction. Use only when the README and repository files leave a narrow reproduction-critical gap and the task is to resolve a specific paper detail such as dataset split, preprocessing, evaluation protocol, checkpoint mapping, or runtime assumption from primary paper sources while recording conflicts. Do not use for general paper summary, repo scanning, environment setup, command execution, title-only paper lookup, or replacing Renv-and-assets-bootstraplllllllama450KRigor Setup skill for README-first deep learning repo reproduction. Use when the task is specifically to prepare a conservative conda-first environment, checkpoint and dataset path assumptions, cache location hints, and setup notes before any run on a README-documented repository. Do not use for repo scanning, full orchestration, paper interpretation, final run reporting, or generic environment setup that is not tied to a specific reproduction target.ai-research-explorelllllllama311KRigor Explore compatible skill slug for meaningful and potentially novel deep learning research candidates. Use when the researcher has chosen the task family, dataset, benchmark, evaluation method, provided SOTA references, and wants candidate-only exploration on top of `current_research` with auditable repo understanding, idea gating, fair comparison, and governed experiments written to `explore_outputs/`. Do not use for README-first trusted reproduction, open-ended direction finding, narrow c
