What problem does it solve? Keeping a local LaTeX paper directory and an Overleaf project in sync is error-prone: collaborators edit in the Overleaf web UI while local audit and editing pipelines run on a separate copy, causing divergence, lost changes, and leaked authentication tokens. This Skill provides a controlled two-way sync workflow with diff review, conflict handling, and token security guards. ## Core Features & Use Cases - Two-way Git bridge sync: Pull collaborator edits from Overleaf and push local changes back using the official Overleaf Git bridge, with rsync between the working paper directory and the Overleaf clone. - Per-hunk diff review protocol: Classify each pulled change (editorial fix, numerical change, new citation, half-finished sentence) and decide whether to sync it and which audit to re-run. - Token security by design: One-time interactive setup stores the Overleaf token in the OS keychain, strips it from remote URLs, and installs a pre-commit hook that blocks token patterns from being committed. - Use Case: A co-author edits your paper on Overleaf overnight; you run a pull, review the diff hunks, sync the clean changes into your local paper directory, re-run claim and citation audits on changed numbers, then push your local revisions back for the team. ## Quick Start Ask the assistant to set up Overleaf sync for your paper directory by providing your Overleaf project ID, then run the printed setup command in your own terminal.
