← ClaudeAtlas

overleaf-paper-synclisted

Manage Overleaf-backed LaTeX papers mirrored to GitHub with bidirectional GitHub Actions sync. Use for Overleaf git tokens, paper version control, GitHub mirrors, divergence or merge conflicts between Overleaf and Git, repos with sync-overleaf/pull-from-overleaf workflows or sync helpers, collaborator onboarding, and named paper instances listed in references/instances.md.
bingran-you/bingran-you · ★ 2 · AI & Automation · score 73
Install: claude install-skill bingran-you/bingran-you
# Overleaf Paper Sync Manage a LaTeX paper that lives on Overleaf by mirroring it on GitHub, with both directions kept in sync automatically by two GitHub Actions workflows. The point is to get Overleaf's editor + preview while keeping GitHub's version control, PR review, and tooling — without paying for Overleaf's built-in GitHub integration. ## The mental model Overleaf is a great editor (live preview, real-time collab, browser-based). It's a weak version control system. GitHub is the inverse. This setup keeps **Overleaf as the editor of record** and **GitHub as the source of version truth**, connected by two automated paths: 1. **GitHub → Overleaf (push trigger).** Every push to GitHub's `master` runs `.github/workflows/sync-overleaf.yml`, which `git push`es to Overleaf's git endpoint within seconds. 2. **Overleaf → GitHub (cron + on-demand).** `.github/workflows/pull-from-overleaf.yml` runs hourly on a cron and on manual trigger. It fetches Overleaf, compares HEADs, and: - if Overleaf has new commits (a web edit), fast-forwards GitHub master onto them and pushes, - if GitHub is already ahead, does nothing — the other workflow handles that direction, - if both sides have unique commits, fails loudly with resolution instructions, because automated merges of LaTeX produce silently-broken papers. Local clones also get a `sync.ps1` / `sync.sh` helper that the user runs **before each editing session**: it triggers the pull workflow, waits for it to finish, and fa