review-overleaf — Claude Code and Codex skill
review-overleaf — a skill for Claude Code and Codex that pulls unresolved reviewer comments from an Overleaf project, locates each in your local LaTeX repository, and proposes edits.
Apache-2.0 ★ 1,216 updated 2026-11-09
/plugin marketplace add fcakyon/claude-codex-settings
/plugin install overleaf-skills@claude-settingsWhat review-overleaf does
The skill works step by step: it asks for a project ID (you can give a hex ID, full URL, or project name—it looks it up), then fetches all unresolved comment threads via overleaf.py as JSON. For each comment linked to a line in a local .tex file, it shows context, proposes a concrete edit to the text, and applies it. Once all edits are done, it displays the full git diff and lists any comments it could not anchor to a file.
Authentication works automatically: the skill looks for a session in env vars, cookie files, or a logged-in Chrome. If the session expires, it directs you to the setup skill. For read-only projects, it warns that syncing back to Overleaf requires manual copy-paste. If your Overleaf project has GitHub sync, you can push changes back to Overleaf and recompile using --sync-github --compile, then download the updated PDF.
The skill does not upload files directly to Overleaf—only local edits. Multi-line comments and bibliography edits fall outside the first version's scope.
What it helps with
- fetch all open reviewer comments from Overleaf into a local repository
- find which LaTeX line each comment refers to
- apply reviewer edits to the source code automatically
- sync the edited project back to Overleaf via GitHub
Example prompts for the agent
- Tell the assistant: “Pull my Overleaf reviews and apply them locally”
- “Sync comments from the Overleaf project with ID 5f3a2b1c0d9e8f7a6b5c4d3e”
- “Show me what reviewers suggested in Overleaf for this LaTeX file and apply their edits”
How to install review-overleaf
1Plugin marketplace
/plugin marketplace add fcakyon/claude-codex-settings/plugin install overleaf-skills@claude-settingsThis installs the whole overleaf-skills plugin with all its skills
2Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill review-overleaf -a claude-code3Manually: put the files in place
~/.claude/skills/review-overleaf/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/review-overleaf/
1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill review-overleaf -a codex2Manually: put the files in place
.agents/skills/review-overleaf/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill review-overleaf -a cursor2Manually: put the files in place
.cursor/skills/review-overleaf/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install fcakyon/claude-codex-settings plugins/overleaf-skills/skills/review-overleaf2Manually: put the files in place
.github/skills/review-overleaf/SKILL.md1Skills CLI (Vercel)
npx skills add fcakyon/claude-codex-settings --skill review-overleaf -a gemini-cli2Platform CLI
gemini skills install https://github.com/fcakyon/claude-codex-settings --path plugins/overleaf-skills/skills/review-overleafManually: put the files in place
.devin/skills/review-overleaf/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about review-overleaf
How do I install review-overleaf in Claude Code?
Run /plugin marketplace add fcakyon/claude-codex-settings, then /plugin install overleaf-skills@claude-settings, then npx skills add fcakyon/claude-codex-settings --skill review-overleaf -a claude-code. Verify the skill file appears at ~/.claude/skills/review-overleaf/SKILL.md.
How do I install the skill in Codex?
Run npx skills add fcakyon/claude-codex-settings --skill review-overleaf -a codex. The skill installs to .agents/skills/review-overleaf/SKILL.md.
What happens if a comment cannot be found in my local file?
The skill collects such comments in a separate list with a text preview and doc_id so you can locate them manually or address them through the Overleaf web UI.
Source text
SKILL.md · Apache-2.0
---
name: review-overleaf
description: This skill should be used when user asks to "fetch overleaf review comments", "address overleaf reviews", "apply overleaf comments", "review my overleaf paper", "sync overleaf feedback to local", "what comments are on my overleaf doc", or wants to act on Overleaf reviewer feedback in a local git-tracked LaTeX repo.
---
# Review Overleaf
Pull unresolved review threads from an Overleaf project, locate each in the local repo, propose edits the user reviews, and apply them. Does not push back to Overleaf — the web UI is still the place to mark threads resolved after the user verifies the local change.
Commands use `${CLAUDE_PLUGIN_ROOT}`, this plugin's root. Claude Code fills it in. Codex and Antigravity leave it as written, so replace it with the absolute path two directories above this SKILL.md.
## Step 1: Resolve project ID
Accept any of:
- Raw 24-char hex ID (`^[0-9a-f]{24}$`)
- Full URL like `https://www.overleaf.com/project/<id>`, passed to the script as is
- Project name in quotes — call:
```bash
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/overleaf.py --list-projects
```
Each line is `<24-hex> <accessLevel> <name>`. Fuzzy-match the name. If multiple match, AskUserQuestion to disambiguate.
If the user has not given a project ID at all, run `--list-projects` and show the user the table so they can pick one.
## Step 2: Auth
The script finds a session by itself (env var, cookie file, then a logged-in Chrome via `agent-browser`). If any call exits with the refresh hint, point the user at the `setup` skill and stop.
## Step 3: Access-level guard
If the project ID came from name resolution, check the matched entry's `accessLevel`. If `readOnly`, warn:
> Project is read-only. You can edit local files but cannot sync them back to Overleaf via the web UI; you would need to copy-paste manually. Continue?
For `owner`, `readAndWrite`, or `review`, proceed silently.
## Step 4: Fetch comments
```bash
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/overleaf.py --json --repo . < project-id > --unresolved-only
```
Parses to a JSON array. Each record has: `thread_id`, `doc_id`, `snippet`, `offset`, `resolved`, `messages` (list of `{user, ts, content}`), `file`, `line`. The `file` and `line` are null when the snippet did not match any local `*.tex`.
## Step 5: Edit loop
For each record where `file` is non-null:
1. `Read` the file at `line` ± 5 lines for context.
2. Summarize the comment thread in one sentence: who said what.
3. Propose a concrete edit grounded in the comment text. If the comment is a question (e.g., "did you mean X?"), the edit should answer it in the prose; if it's a correction (e.g., "wrong notation"), the edit should make the correction.
4. Apply via `Edit`. Do not batch — one comment, one edit, then move on.
Skip records where `file` is null (snippet did not map). Collect them in an `<unmapped>` list.
## Step 6: Wrap up
After the loop:
1. Run `git diff` and show the user the full set of changes.
2. List the `<unmapped>` records (if any) with `doc_id` + snippet preview, so the user can hunt them manually.
3. Suggest a commit message in the style: `address overleaf review: <one-line summary of the changes>`. Do NOT auto-commit. The user can run `/github-dev:commit-staged` or commit by hand.
4. Remind the user to mark the addressed threads as resolved in the Overleaf web UI once they verify the local diff.
5. If the project has Overleaf GitHub sync and the user pushed the commit, offer to pull it into Overleaf and recompile:
```bash
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/overleaf.py <project-id> --sync-github --compile
```
Prints `SYNC pull <repo> (<n> commit(s))` and `COMPILE <status> (<pages> pages, ..., errors=<n>)`. Add `--download-pdf <path>` to save the PDF, or `--push "<message>"` to push Overleaf-side edits to GitHub instead of pulling.
## Non-goals
- No file uploads to Overleaf. Changes reach Overleaf only through its GitHub sync (`--sync-github`).
- No thread resolution in Overleaf (web UI only).
- No `.bib` edits unless a comment specifically targets a citation.
- No multi-line snippets that span paragraph breaks — those land in `<unmapped>` for v1; the snippet matcher is line-anchored.
## Pairs naturally with
- `github-dev` — `/github-dev:commit-staged` after the edit loop, `/github-dev:create-pr` if the project is collaborative.
© Fatih C. Akyon · Apache-2.0 · fcakyon/claude-codex-settings