review-overleaf

Featured

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.

Code & Development 1,141 stars 108 forks Updated today Apache-2.0

Install

View on GitHub

Quality Score: 93/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# 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. ## 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>` — extract via regex - Project name in quotes — call: ```bash python3 ${CLAUDE_PLUGIN_ROOT}/scripts/overleaf_reviews.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: Cookie precheck If `~/.claude/overleaf-skills/cookie` does not exist, tell the user to "set up overleaf" (which triggers the `setup` skill) and stop. If it exists but auth fails (the next script call returns a refresh hint), point at the same 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 ${CLAU...

Details

Author
fcakyon
Repository
fcakyon/claude-codex-settings
Created
1 years ago
Last Updated
today
Language
Python
License
Apache-2.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

review-skill

Reviews and audits an existing skill, then tightens it — a fast, static, read-only audit of a `SKILL.md`'s triggering, scope, structure, prose, and domain accuracy, with severity-ranked findings applied on approval. Use whenever the user wants to review, critique, audit, lint, tighten, or improve a skill they already have, fine-tune a skill drafted with skill-creator, or asks why a skill is too verbose, won't trigger, or feels off — even when they just paste a SKILL.md and ask for feedback. Defers the empirical loop (running evals, benchmarking, the automated description optimizer, packaging) to skill-creator; this is the static counterpart that reads rather than measures.

0 Updated today
azborgonovo
Code & Development Listed

review

Use automatically when the user asks to review code, review the current diff, inspect a PR/branch/commit range, run a contextual code review, "review la PR", "review ce diff", or "fais une review". Loads repo instructions such as AGENTS.md, CLAUDE.md, Copilot instructions, path-scoped rules, and PR/spec context before producing severity-ranked findings. Do not use for commit creation, PR creation, branch creation, or implementing fixes unless the user explicitly asks to address findings.

1 Updated 2 days ago
g-bastianelli
Code & Development Listed

aio-code-review

Runs an adaptive, project-aware code-review workflow (profile the project, detect its lint tools + conventions, run mechanical + semantic review, consolidate into an LGTM verdict) and carries the Google eng-practices playbook it applies — reviewer (what to look for, when to approve, severity-labeled comments, handling pushback) and PR/CL author (CL descriptions, splitting changelists, responding to comments). Use when reviewing or authoring a PR/MR/CL/diff, running a code review, deciding LGTM or LGTM threshold, authoring a merge request, assessing code health, handling a hotfix review, or replying to review feedback.

4 Updated 1 weeks ago
aiocean