review-overleaf
FeaturedThis 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.
Install
Quality Score: 93/100
Skill Content
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
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.
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.
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.