review-overleaf

Fetches unresolved Overleaf review comments and applies them as edits to local LaTeX files.

1.1k|107|Updated Jul 9, 2025
One-click install
npx skills add https://github.com/fcakyon/claude-codex-settings --skill review-overleaf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-overleaf
Source: https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/overleaf-skills/skills/review-overleaf
Command: npx skills add https://github.com/fcakyon/claude-codex-settings --skill review-overleaf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Collaborators leave review comments on Overleaf, but acting on them means manually hunting through a local git-tracked LaTeX repo to find each commented passage. This Skill pulls unresolved review threads from an Overleaf project, maps each comment to the matching local .tex file and line, and applies proposed edits one at a time.

Core Features & Use Cases

  • Comment Fetching and Mapping: Retrieves unresolved review threads via a Python script and anchors each snippet to a local file and line number.
  • Guided Edit Loop: Reads surrounding context, summarizes each thread, proposes a concrete edit, and applies it individually for user review.
  • Project Resolution and Access Guards: Accepts a raw project ID, URL, or fuzzy project name, checks cookie authentication, and warns on read-only projects.
  • Use Case: A co-author leaves a dozen comments on your Overleaf paper overnight. Run this Skill to pull every unresolved thread, apply the suggested corrections to your local repo, review the git diff, and commit the changes.

Quick Start

Fetch the unresolved review comments from my Overleaf paper and apply them to this local LaTeX repository.

Frequently Asked Questions about review-overleaf

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fetch Overleaf review comments into my local git repo?

Provide the Overleaf project ID, URL, or project name, and the Skill runs a Python script that returns unresolved comment threads as JSON. Each thread is matched to a local .tex file and line so edits can be applied directly in your repo.

How do I apply Overleaf reviewer feedback to local LaTeX files?

The Skill loops through each mapped comment, reads the surrounding lines for context, proposes a concrete edit based on the comment text, and applies it one at a time. Afterward it shows the full git diff so you can verify every change before committing.

Does this sync changes back to Overleaf automatically?

No, the Skill only edits local files and never writes back to Overleaf. You must mark threads as resolved in the Overleaf web UI yourself after verifying the local diff, and read-only projects require manual copy-paste to sync.

Why are some Overleaf comments not mapped to local files?

Comments whose snippets do not match any local .tex file, or that span paragraph breaks, cannot be line-anchored and are collected in an unmapped list. The Skill reports these with their doc ID and snippet preview so you can locate them manually.

What happens if my Overleaf session cookie is missing or expired?

The Skill checks for a cookie file at ~/.claude/overleaf-skills/cookie before fetching comments. If it is missing or authentication fails, it directs you to run the companion setup skill to re-authenticate and then stops.