revise-paper
Apply revisions from a review report to a manuscript.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Apply revisions from a review report to a manuscript.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
End-to-end empirical data analysis workflow for R or Python projects.
Find and assess datasets for a research question.
Repository-wide consistency audit for skills, hooks, rules, and docs.
Systematic literature review workflow using parallel librarian agents.
Structured interview and project-spec workflow for new research ideas.
Proofreading workflow for academic manuscripts and papers.
| name | revise-paper |
| description | Apply revisions from a review report to a manuscript. |
Systematically apply revisions from a review report to a manuscript. Follows the prose-track rule: never edit without user approval.
Input: $ARGUMENTS — path to a review report, or leave blank to auto-detect.
If $ARGUMENTS is provided, use that path. Otherwise search for:
quality_reports/paper_review_*.mdquality_reports/*_substance_review.mdquality_reports/*_proofread.mdIf multiple reports are found and there are 2-3 clear candidates, use request_user_input in Plan mode for a single-choice prompt; otherwise ask the user conversationally.
Read the review report and extract the manuscript path from its File: field.
If the file does not exist at that path, search for likely candidates in:
manuscripts/**/*.texmanuscripts/**/*.qmdIf multiple manuscripts remain plausible, ask the user to choose.
Read the full manuscript before proposing changes.
Extract all actionable items and group them by priority:
| Priority | Source Section | Meaning |
|---|---|---|
| Critical | Major Concerns marked critical, blocking, fatal, or equivalent | Must fix before submission |
| Major | Major Concerns and Referee Objections | Strong referee-facing revisions |
| Minor | Minor Concerns and Specific Comments | Polish and cleanup |
For each item, capture:
Present the plan grouped by priority:
## Revision Plan
### Critical (N items) — must fix
1. [MC1: Title] — Section X — [brief description of fix]
### Major (N items) — should fix
1. [MC2: Title] — Section Y — [brief description of fix]
### Minor (N items) — polish
1. [mc1: Title] — Section Z — [brief description of fix]
Total: N revisions across M sections.
Do NOT start editing until the user approves the plan or explicitly selects which items to address.
Work through approved items in this order:
For each approved revision:
If the user approves only part of the plan, skip the deferred items and record them in the summary.
After applying the approved revisions, run a focused proofreading pass on the revised sections using agents/proofreader.md as the checklist.
By default, do this inline. If the user explicitly requested delegated review, you may use the proofread workflow or proofreader role separately.
Summarize any new issues introduced by the revisions.
Create quality_reports/ if it is missing before saving.
Save to quality_reports/revision_summary_[paper-name].md:
# Revision Summary: [Paper Name]
**Date:** [YYYY-MM-DD]
**Review report used:** [path]
**Manuscript:** [path]
## Revisions Applied
| # | Priority | Issue | Section | Status |
|---|----------|-------|---------|--------|
| 1 | Critical | [title] | Section X | APPLIED |
| 2 | Major | [title] | Section Y | APPLIED |
| 3 | Minor | [title] | Section Z | DEFERRED — user chose to skip |
## Issues Deferred
- [Item]: [reason deferred]
## Post-Revision Review Findings
- [Any new issues introduced by edits]
## Recommended Next Steps
- **`quality-gate`** — verify claim consistency after edits
- **`validate-bib`** — check citations if references were added or changed
- **`review-paper`** — run a fresh review to confirm the issues are resolved