paper-revision

name: paper-revision description: Learn writing style from reference papers and revise your LaTeX draft with reviewer feedback triggers: - "paper revision" - "revise my paper" - "learn writing style" - "academic writing" - "polish my paper" - "improve my writing" - "修改论文" - "润色论文" - "latex revision" - "reviewer comments" - "审稿意见" - "rebuttal" - "response to reviewers" agent: writer model: sonnet

Paper Revision Skill (LaTeX-Enhanced)

Learn writing style, language patterns, and structure from reference papers, then apply those patterns to revise your LaTeX manuscript. Supports direct editing of .tex files and integrates with LaTeX editor workflows.

When to Use

This skill activates when:

• User wants to upload reference papers for style learning
• User needs help revising a LaTeX draft to match academic writing conventions
• User wants to improve the language quality of their paper
• User asks to "learn the writing style" from papers
• User wants their paper "polished" or "improved"
• User is working with LaTeX files and needs direct .tex editing

What It Does

This skill follows a three-phase workflow with LaTeX-specific enhancements:

Phase 0: Reviewer Comments (Optional)

Input: User provides reviewer comments and specifies priorities

Workflow:

1. Parse reviewer comments (from PDF, TXT, or pasted text)
2. Categorize comments by type:
   • Major concerns - Require significant changes or experiments
   • Minor concerns - Clarifications, typos, additional citations
   • Misunderstandings - Reviewer missed something, needs clarification
3. User specifies which reviewers to prioritize (e.g., "focus on Reviewer 2's concerns")
4. Generate a revision action plan mapped to each comment

Folder Structure:

{worktree}/
├── .omc/
│   └── papers/
│       ├── reviews/          # Reviewer comments
│       │   ├── reviewer-1.txt
│       │   ├── reviewer-2.txt
│       │   ├── reviewer-3.txt
│       │   └── meta-review.pdf
│       └── response/         # Generated response letter
│           └── response-to-reviewers.tex

Phase 1: Reference Papers Folder Setup

Folder Structure:

{worktree}/
├── .omc/
│   └── papers/
│       ├── refs/           # Reference papers (PDF or text)
│       │   ├── ref-1.pdf
│       │   ├── ref-2.pdf
│       │   └── ref-3.pdf
│       └── profiles/       # Generated style profiles
│           └── style-profile.md
├── latex/
│   ├── main.tex            # Main LaTeX file
│   ├── chapters/           # Chapter files
│   ├── sections/           # Section files
│   └── references.bib      # Bibliography
└── revised/
    └── draft-revised.tex   # Output revised draft

User Workflow:

1. Create .omc/papers/refs/ folder in your project
2. Place 2-5 reference papers (PDF format) in the folder
3. Skill automatically detects and analyzes all papers in the folder

Phase 2: Style Analysis

Analysis Process:

1. PDF Extraction - Use the Read tool to extract text from PDF papers

   • The Read tool natively supports PDF files - use it directly
   • For large PDFs (>10 pages), use the pages parameter to read in chunks (e.g., pages: "1-10", "11-20")
   • Read each PDF in .omc/papers/refs/ sequentially until all content is extracted

2. Writing Pattern Analysis:

   • Sentence structure and length preferences
   • Transition phrases and connectors
   • Technical terminology usage
   • Paragraph organization patterns
   • Citation style (author-year, numbered, etc.)
   • Abstract and introduction structure
   • Results/discussion language patterns

3. LaTeX-Specific Patterns:

   • Section/subsection organization
   • Figure/table referencing style
   • Equation presentation
   • Citation commands (\cite, \citet, \citep)
   • Cross-referencing patterns (\ref, \label)

Phase 3: Style Profile Creation

Create a structured style profile at .omc/papers/profiles/style-profile.md:

# Style Profile

## Vocabulary Patterns
- Academic phrases: "we propose", "our results demonstrate", ...
- Hedging: "suggests", "may indicate", "potentially"
- Certainty: "clearly", "demonstrates", "establishes"

## Sentence Patterns
- Average sentence length: 20-25 words
- Passive/Active ratio: 40/60
- Common structures: [Pattern examples]

## LaTeX Patterns
- Citation style: \citet{author} for narrative, \citep{author} for parenthetical
- Section structure: Introduction → Related Work → Method → Experiments → Conclusion
- Figure refs: "Figure~\ref{fig:name}" (capitalized)
- Equation refs: "Eq.~\eqref{eq:name}"

## Section Templates
### Abstract
- Sentence 1: Problem statement
- Sentence 2: Gap identification
- Sentence 3: Proposed approach
- Sentence 4: Key results
- Sentence 5: Implications

### Introduction
- Paragraph 1: Broad context
- Paragraph 2: Specific problem
- Paragraph 3: Limitations of prior work
- Paragraph 4: Our contributions (bulleted)

Phase 4: LaTeX Draft Revision

Direct .tex File Editing:

The skill can directly read and modify LaTeX files:

1. Preserve LaTeX Structure:

   • Keep all \label{} and \ref{} intact
   • Preserve \cite{} commands
   • Maintain math environments ($$, \[, \begin{equation})
   • Don't modify figure/table environments

2. Apply Style Improvements:

   • Revise text content only (not LaTeX commands)
   • Improve sentence flow in paragraphs
   • Enhance academic tone
   • Fix grammar and language issues
   • Match learned section patterns

3. Track Changes:

   • Use LaTeX diff format: \deleted{old} and \added{new}
   • Or create a .tex.diff file with changes
   • Generate a summary document explaining key revisions

Agent Delegation

Reviewer Comment Processing

Task(
  subagent_type="oh-my-claudecode:writer",
  model="sonnet",
  name="reviewer-comment-analyzer",
  prompt="REVIEWER COMMENT ANALYSIS TASK

Analyze reviewer comments and create a revision action plan.

Input:
- Reviewer comments from .omc/papers/reviews/
- User priorities (e.g., 'focus on Reviewer 2's major concerns')

Analysis Tasks:
1. Parse and categorize each comment:
   - Major: Requires significant changes, new experiments, or major rewrites
   - Minor: Clarifications, typos, additional references, wording changes
   - Misunderstanding: Reviewer missed something, needs polite clarification
2. Map comments to paper sections (Introduction, Method, Experiments, etc.)
3. Estimate effort for each change (LOW/MEDIUM/HIGH)
4. Identify conflicting comments (reviewers disagree)

Output:
- Revision plan at .omc/papers/reviews/revision-plan.md
- Comment-to-section mapping table
- Priority-ordered action items
"
)

Response Letter Generation

Task(
  subagent_type="oh-my-claudecode:writer",
  model="sonnet",
  name="response-letter-writer",
  prompt="RESPONSE LETTER GENERATION TASK

Generate a professional response letter to reviewers.

Input:
- Original reviewer comments
- List of changes made (from revision-plan.md)
- Revised manuscript sections

Output:
- Response letter at .omc/papers/response/response-to-reviewers.tex
- Format: For each comment, provide:
  1. Reviewer's comment (quoted)
  2. Our response (polite, detailed)
  3. Changes made (with line numbers)
  4. Pointer to revised text

Tone: Professional, grateful, non-defensive
"
)

Style Analysis and Revision

Task(
  subagent_type="oh-my-claudecode:writer",
  model="sonnet",
  name="latex-style-analyzer",
  prompt="LATEX PAPER STYLE ANALYSIS TASK

Analyze reference papers and extract writing style patterns with LaTeX-specific focus.

Input: Reference papers from .omc/papers/refs/

Analysis Tasks:
1. Extract text content from PDF papers
2. Identify vocabulary patterns (academic phrases, hedging, certainty)
3. Analyze sentence structures (length, complexity, voice)
4. Map paragraph organization and transitions
5. Document LaTeX-specific patterns:
   - Citation commands used
   - Section/subsection structure
   - Figure/table/equation referencing style
6. Extract abstract and introduction templates

Output: Style profile at .omc/papers/profiles/style-profile.md"
)

Task(
  subagent_type="oh-my-claudecode:writer",
  model="sonnet",
  name="latex-paper-reviser",
  prompt="LATEX PAPER REVISION TASK

Revise the LaTeX draft using the learned style profile.

Input:
- Draft: latex/main.tex (or specified .tex file)
- Style profile: .omc/papers/profiles/style-profile.md

Revision Rules:
1. PRESERVE all LaTeX commands (\cite, \ref, \label, math, figures, tables)
2. MODIFY only text content between commands
3. Apply vocabulary patterns from style profile
4. Improve sentence flow and academic tone
5. Match section structure patterns

Output:
- Revised .tex file with tracked changes
- Change summary document

Workflow

Step 0: Setup Reviewer Comments (Optional)

# Create reviewer comments folder
mkdir -p .omc/papers/reviews
mkdir -p .omc/papers/response

User places reviewer comments:

.omc/papers/reviews/
├── reviewer-1.txt
├── reviewer-2.txt
├── reviewer-3.txt
└── meta-review.pdf   (optional)

Specify priorities:

/paper-revision review --focus "Reviewer 2" --focus "Reviewer 3's major concerns"

Step 1: Analyze Reviewer Comments

Skill invocation:

/paper-revision analyze-reviews

Actions:

• Parse all reviewer comments
• Categorize by type (Major/Minor/Misunderstanding)
• Map to paper sections
• Generate revision plan at .omc/papers/reviews/revision-plan.md

Step 2: Setup Reference Folder

# User creates reference folder
mkdir -p .omc/papers/refs
mkdir -p .omc/papers/profiles

User places reference papers:

.omc/papers/refs/
├── acl-paper-1.pdf
├── acl-paper-2.pdf
└── acl-paper-3.pdf

Step 3: Analyze References

Skill invocation:

/paper-revision analyze .omc/papers/refs/

Actions:

• Scan .omc/papers/refs/ for all PDF files
• Extract text from each paper
• Analyze writing patterns
• Generate style profile at .omc/papers/profiles/style-profile.md

Step 4: Specify LaTeX Draft

User provides the LaTeX file to revise:

/paper-revision revise latex/main.tex

Or specify a chapter/section:

/paper-revision revise latex/chapters/method.tex

When reviewer comments are available:

/paper-revision revise latex/main.tex --with-reviews

This will prioritize changes based on reviewer feedback.

Step 5: Apply Revision

Actions:

• Read the specified .tex file
• Apply style profile
• Address reviewer comments (if provided)
• Preserve LaTeX structure
• Write revised output to revised/ folder

Step 6: Generate Response Letter (Optional)

When reviewer comments are provided:

/paper-revision generate-response

Actions:

• Read revision changes
• Generate point-by-point response
• Output to .omc/papers/response/response-to-reviewers.tex

Step 7: Review and Iterate

Output delivered:

• revised/main-revised.tex - Full revised LaTeX file
• revised/changes.md - Summary of all changes
• revised/main-diff.tex - Version with \added{} and \deleted{} markup

User can:

• Compile the revised .tex to verify formatting
• Request specific section re-revision
• Accept/reject individual changes

Tool Usage

• Use Read to extract content from PDF and .tex files (Read tool natively supports PDF)
• For large PDFs, use pages parameter: Read(path, pages="1-10")
• Use Edit to make surgical changes to .tex content
• Use Write to save style profiles and revised drafts
• Use Glob to find all .tex files and PDFs in the project
• Use Task with oh-my-claudecode:writer agent for analysis and revision
• Use project_memory_add_note to persist style profiles

File Locations

LaTeX-Specific Handling

What Gets Preserved

% All commands preserved exactly
\cite{author2023}
\ref{fig:architecture}
\label{sec:method}
\begin{equation}
  E = mc^2
\end{equation}
\begin{figure}[t]
  \centering
  \includegraphics{architecture.pdf}
  \caption{System architecture}
  \label{fig:architecture}
\end{figure}

What Gets Revised

% Text content between commands gets improved
% BEFORE:
\section{Introduction}
In this paper we do thing. The method is good.
We get better results than before.

% AFTER (revised with academic tone):
\section{Introduction}
In this paper, we present a novel approach to X.
Our method demonstrates significant improvements over prior work.
Experimental results show that our approach achieves state-of-the-art performance.

Citation Style Detection

The skill detects and matches the citation style from reference papers:

Examples

Escalation And Stop Conditions

• Large PDF handling: If PDF > 20 pages, read in chunks using pages parameter (e.g., "1-15", "16-30")
• Wrong file type: If user places PDFs in latex/ directory, clarify the folder structure
• Compilation issues: If revised .tex doesn't compile, investigate:
  • Did we accidentally modify a LaTeX command? → Fix immediately
  • Encoding issues? → Ensure UTF-8
• Large files: If .tex > 50 pages, suggest chapter-by-chapter revision
• Bibliography: Do NOT modify .bib files automatically - citation style should be preserved

Final Checklist

• Reference papers placed in .omc/papers/refs/
• Style profile generated at .omc/papers/profiles/style-profile.md
• Target .tex file identified
• All LaTeX commands preserved (citations, references, math, figures, tables)
• Text content revised to match style profile
• Changes tracked with \added{} / \deleted{} or separate diff file
• Revised file compiles without errors (user verifies)
• Change summary document provided

Configuration

Optional settings via ~/.claude/.omc-config.json:

{
  "paper-revision": {
    "refsFolder": ".omc/papers/refs/",
    "profileFolder": ".omc/papers/profiles/",
    "latexSourceFolder": "latex/",
    "outputFolder": "revised/",
    "minReferencePapers": 2,
    "maxReferencePapers": 5,
    "trackChanges": true,
    "diffFormat": "latex-diff",
    "preserveBib": true
  }
}

Quick Start

# 1. Setup folders
mkdir -p .omc/papers/refs .omc/papers/profiles revised

# 2. Place 2-5 reference papers (PDF) in .omc/papers/refs/

# 3. Invoke skill
/paper-revision

# Or be specific:
/paper-revision analyze .omc/papers/refs/
/paper-revision revise latex/main.tex

# 4. Review output in revised/

Integration with LaTeX Editors

VS Code + LaTeX Workshop

1. Install "LaTeX Workshop" extension
2. After revision, open revised/main-revised.tex
3. Use built-in diff viewer to compare with original
4. Compile to verify formatting

Overleaf

1. Download revised/main-revised.tex
2. Upload to Overleaf project
3. Use Overleaf's "Track Changes" feature (if available)
4. Compile to verify

Vim/Neovim + vimtex

1. Set vimtex to compile from revised/ folder
2. Use :VimtexCompile to verify
3. Use fugitive.vim for diff viewing

Task: {{ARGUMENTS}}