This repository is designed to work with both Claude Code and Codex while preserving the original proofreading philosophy.
The detailed instructions live in two prompt files. You can use them directly in a session, or copy/merge them into Codex-oriented workspace instructions such as AGENTS.md.
The workflow remains two-phase: the agent detects and lists all issues with unique numbers [1], [2], [3]..., then waits. The user selects which issues to fix or discard before any file is modified.
These prompts are distilled from years of hands-on paper reviewing and mentoring experience by Hyungtae Lim, a researcher in robotics and 3D perception.
- 📝 Associate Editor, IEEE Robotics and Automation Letters (RA-L)
- 🌟 RSS Pioneer 2024
- 🎖️ ICRA 2025 Outstanding Reviewer — selected from 7,400+ reviewers
- 📄 Conducted 100+ paper reviews across top robotics and CV venues
The review rules in these prompts reflect the standards expected at top robotics and computer vision venues, refined through real paper reviews and publications across ICRA, IROS, RSS, CVPR, ICCV, NeurIPS, AAAI, RA-L, T-RO, IJRR, T-PAMI, T-IV, etc.
Optional Codex coordinator instructions for the workflow:
- detects first and waits before editing
- chooses between workspace audit and paper proofreading
- reads the full LaTeX workspace recursively
- applies only approved fixes in Phase 2
- points Codex to the authoritative prompt files
LaTeX infrastructure audit — detailed checklist for workspace-level errors before submission.
| Check | Description |
|---|---|
| C1 | Preamble configuration (hyperref, cleveref, caption setup) |
| C2 | Package load order & conflicts |
| C3 | Macro safety, \methodname consistency, subscript macros, \etalcite |
| C4 | Cross-reference consistency (multi-ref, subcaption Fig. 5(a) format) |
| C5 | Label naming conventions, duplicate labels |
| C6 | Citation & bibliography integrity, duplicate BibTeX keys |
| C7 | Figure & table safety (missing files, dummy figures, label placement) |
| C8 | Hidden human errors (TODOs, inconsistent naming, \vspace hacks) |
| C9 | Academic writing patterns detectable in source (\ie, \eg, units) |
Paper content proofreading — detailed checklist for strict conference-level review.
| Category | Description |
|---|---|
| A | Language & grammar, tense consistency, Related Work tense |
| B | Language quality & awkward expression: typos, nominalization, filler phrases, citation-as-noun style |
| C | Scientific clarity: overclaiming, "significantly", unsupported claims |
| D | Structure & flow: intro claims, experiment purpose, equation narrative |
| E | Figure/table/caption review: self-containedness, reference order, quantitative consistency |
| F | LaTeX formatting: units, thousand separators, \ie/\eg macros |
| G | Abstract (WHY→PROBLEM→HOW→RESULTS) & conclusion quality |
| H | Notation consistency: symbol overload, boldface vectors, coordinate frames |
| I | Hyphenation: compound adjectives, -ly adverb rule |
There are two supported ways to use this repository.
git clone https://github.com/LimHyungTae/awesome-claudecode-paper-proofreading.git ~/awesome-claudecode-paper-proofreadingThese prompts are used from inside your paper workspace, not from inside this repository.
The @ file reference in Claude Code resolves paths relative to the directory where claude is launched.
cd /path/to/your/paper
claudeIn the Claude Code session, reference the prompt by its absolute path, then attach your paper files:
@~/awesome-claudecode-paper-proofreading/prompts/01_latex_workspace_review.md
@main.tex @shortcuts.tex
Provide the root .tex file and the compiled PDF. The prompt automatically instructs Claude to follow all \input{...} calls and read every included section file:
@~/awesome-claudecode-paper-proofreading/prompts/02_paper_proofreading.md
@main.tex @paper.pdf
Why the PDF? The compiled PDF lets Claude cross-check two things invisible in source alone:
- Figure placement — figures displaced far from their in-text reference
- PDF-level annotations — leftover review comments not yet resolved
After Phase 1 output, respond with:
discard 3, 7, 12 ← skip specific issues
fix all critical ← fix only CRITICAL issues
proceed with all ← fix everything
Copy AGENTS.md and the prompts/ directory into your paper workspace:
cp ~/awesome-claudecode-paper-proofreading/AGENTS.md /path/to/your/paper/AGENTS.md
cp -R ~/awesome-claudecode-paper-proofreading/prompts /path/to/your/paper/Launch Codex from the paper root so it can pick up AGENTS.md, then ask for the workflow you want:
Run the LaTeX workspace review on `main.tex`.
or
Proofread `main.tex` against `paper.pdf`.
- Detect first, fix later — the agent never modifies files until the user explicitly confirms
- Modular categories — each check is a labeled block; reorder or disable by editing the table at the top of each prompt
- Real-world patterns — rules extracted from annotated paper reviews across ICRA, RA-L, AAAI, BMVC, and CVPR submissions
- Non-native writer aware — covers patterns common in papers by Korean/Japanese researchers
figures/vspics/— distinguishes final manuscript figures from raw image sources
This setup also works in CI or other non-GUI environments as long as the agent runs from the paper workspace and sees the relevant instructions.
Recommended pattern:
- Check out your paper repository.
- Copy in
AGENTS.mdplusprompts/, or inline the prompt content into one file. - Ask the agent to run the workspace review or proofreading pass.
- paper-writing-checklist — LaTeX workspace guidelines referenced by these prompts in Korean