Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
lingzhi227 avatar

Paper Revision

  • 18 installs
  • 255 repo stars
  • Updated February 27, 2026
  • lingzhi227/claude-skills

This is a copy of paper-revision by lingzhi227 - installs and ranking accrue to the original listing.

Helps with ai & agent building tasks.

About

paper-revision is a Claude Code skill for ai & agent building. It helps solo builders move faster with AI-assisted development.

  • paper-revision
  • AI & Agent Building
  • AI-coding skill

Paper Revision by the numbers

  • 18 all-time installs (skills.sh)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/lingzhi227/claude-skills --skill paper-revision

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs18
repo stars255
Last updatedFebruary 27, 2026
Repositorylingzhi227/claude-skills

What it does

Helps with ai & agent building tasks.

Files

SKILL.mdMarkdownGitHub ↗

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: 1. Extract the specific concern 2. Classify: major revision, minor revision, question, suggestion 3. Map to affected paper section(s) 4. 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: 1. Read the current section 2. Apply targeted edits (preserve surrounding structure) 3. If new experiments needed: use experiment-code skill 4. If new figures/tables needed: use figure-generation / table-generation skills 5. 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

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.