fcakyon/claude-codex-settings / plugins/overleaf-skills/skills/review-overleaf
review-overleaf
VerifiedThis 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:
Each line ispython3 ${CLAUDE_PLUGIN_ROOT}/scripts/overleaf.py --list-projects<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
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:
Readthe file atline± 5 lines for context.- Summarize the comment thread in one sentence: who said what.
- 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.
- 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:
-
Run
git diffand show the user the full set of changes. -
List the
<unmapped>records (if any) withdoc_id+ snippet preview, so the user can hunt them manually. -
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-stagedor commit by hand. -
Remind the user to mark the addressed threads as resolved in the Overleaf web UI once they verify the local diff.
-
If the project has Overleaf GitHub sync and the user pushed the commit, offer to pull it into Overleaf and recompile:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/overleaf.py <project-id> --sync-github --compilePrints
SYNC pull <repo> (<n> commit(s))andCOMPILE <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
.bibedits 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-stagedafter the edit loop,/github-dev:create-prif the project is collaborative.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 465k | Updated | Claude CodeCodex | Verified | Install |
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 465k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 318k | Updated | Claude CodeCodex | Verified | Install |