caveman-review
JuliusBrussee/caveman/skills/caveman-review/SKILL.md
Compressed code review - one line per finding with location, problem and fix. Use for /caveman-review, "review this PR", or "review the diff".
Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
JuliusBrussee/caveman/skills/caveman-review/SKILL.md
Compressed code review - one line per finding with location, problem and fix. Use for /caveman-review, "review this PR", or "review the diff".
opendataloader-project/opendataloader-pdf/.agents/skills/odl-review/SKILL.md
Decide whether an opendataloader-pdf pull request is safe to merge, by its results, inside clear bounds: the change does nothing harmful or hidden; it fixes its target (what the issue or the pull request asks), shown with the code, tests, and runs; and nothing that works on main breaks. If these hold, approve; do not ask for more. Code enforces what must not vary (the trust boundary of the trees, the scan, the earlier decisions, the test-suite comparison, and the verdict itself), you judge the target, the risks, and the checks, and the user approves what cannot be undone. You doubt your plan, the change, and the evidence once. Other people's code runs only in an isolated environment. Use it when the user asks "review #123", "can I merge #123", "is this PR safe", or wants a merge verdict. Also use it to triage all open pull requests ("which PRs should I look at first"). Do not use it to fix an issue. The user approves twice: the plan at the start, and the answers and posts at the end.
Steady7 mentions in 2 weeks
No other project uses it yet
ben-manes/caffeine/.claude/skills/review-change/SKILL.md
Multi-layer adversarial code review of a diff or branch using parallel specialized reviewers with triage
Often used withplan-changeimplement-change
google/adk-python/.agents/skills/adk-review/SKILL.md
Reviews the uncommitted changes in an adk-python working tree and reports correctness, design, public-API stability, test, sample and documentation gaps as a prioritized findings report, fixing them only when asked. Use when the user asks to review local changes, wants a self-review before opening a pull request, asks whether a change breaks the public API or needs tests, samples or docs, or asks what is wrong with the current diff. Required for changes to public APIs, core architecture (Runner, Workflow, BaseNode), new features and major refactors. Don't use for a single style nit (use adk-style), for diagnosing a failing test or a misbehaving agent at runtime (use adk-debug), or for wording a commit message or PR description (use adk-git).
assistant-ui/assistant-ui/.claude/skills/change-review/SKILL.md
Apply assistant-ui's existing review standards to a local change or pull request before submission and after substantive revisions. Use to compare the requested behavior with the diff, trace affected runtime paths, and assess evidence without duplicating repository policy.
Steady4 mentions in 2 weeks
8 projects use a version of this
sgl-project/sglang/.agents/skills/cookbook-review-pr/SKILL.md
Review a pull request against the SGLang Cookbook (docs/, Mintlify) contribution checklist — the config-driven format (per-model config + benchmarks JSX consumed by the shared _deployment.jsx / _playground.jsx engines). Run with /cookbook-review-pr <PR number>.
googleapis/mcp-toolbox/skills/maintainer/review-prs/SKILL.md
Review a GitHub pull request in the googleapis/mcp-toolbox repo against the team's reviewer checklist: PR title/description conventions, linked issue, logic errors and unhandled edge cases, breaking changes, test coverage, docs updates, security (input handling), and new dependencies. Use whenever a maintainer asks you to review, look over, "take a look at", or check whether something is ready to merge in mcp-toolbox, e.g. "review #3703", "can you look at this PR", "is this good to merge", or when they paste an mcp-toolbox PR link. PROPOSE-ONLY: delivers the review in chat for the maintainer to post; never approves, requests changes, comments, labels, or merges on its own.
10 projects use a version of this
metabase/metabase/.claude/skills/clojure-review/SKILL.md
Review Clojure and ClojureScript code changes for compliance with Metabase coding standards, style violations, and code quality issues. Use when reviewing pull requests or diffs containing Clojure/ClojureScript code.
Steady2 mentions in 2 weeks
No other project uses it yet
storybookjs/storybook/.agents/skills/docs-review/SKILL.md
Review, improve, rewrite, author, or plan Storybook documentation in /docs. Use this when asked to review docs, improve a page, rewrite documentation, draft new docs, or advise on docs strategy.
24 projects use a version of this
google/elephant-goldfish-model/distributions/claude/skills/egm-review/SKILL.md
Orchestrates the EGM Goldfish Review Protocol. Used as part of the EGM process to perform design document reviews. Executes five review phases: Initial Zoom Out Review, Comprehension Review, Design Critique, Intermediate Zoom Out Review, and Implementation Readiness.
Steady81 mentions in 2 weeks
No other project uses it yet
lobehub/lobe-chat/.agents/skills/deep-review/SKILL.md
Use for independent PR, diff or branch review; not explanations. Full multi-agent review requires an explicit deep-review request.
dataelement/bisheng/.claude/skills/sdd-review/SKILL.md
对 BiSheng 项目的 SDD 文档执行审查。
4 projects use a version of this
open-gsd/get-shit-done-redux/skills/gsd-review/SKILL.md
Request cross-AI peer review of phase plans from external AI CLIs
4 projects use a version of this
tirth8205/code-review-graph/skills/review-changes/SKILL.md
Perform a structured code review using change detection and impact
Steady6 mentions in 2 weeks
34 projects use a version of this
penpot/penpot/.agents/skills/review-plan/SKILL.md
Plan review flow — evaluate an implementation plan before it is executed, delegating the review to a subagent that follows the plan-review-criteria skill. Use it when the user asks to review a plan, in any phrasing.
Steady6 mentions in 2 weeks
35 projects use a version of this
Often used withimplement-planreview-codebrainstorm
garrytan/gstack/plan-ceo-review/SKILL.md
CEO/founder-mode plan review. (gstack)
Steady13 mentions in 2 weeks
49 projects use a version of this
Often used withplan-tuneios-cleandocument-generate
odoo/odoo/skills/odoo-review/SKILL.md
Review Odoo addon code against the house rules, dispatching each changed file to the matching odoo-guidelines, odoo-web-guidelines, and odoo-security material. Use when reviewing a diff, commit, PR, or module.
No other project uses it yet
bmad-code-org/BMAD-METHOD/skills/bmad-review/SKILL.md
Runs one or more installed review lenses — adversarial critique, edge cases, verification gaps, structure, prose — and reports triaged findings. Use when, and only when, the user asks you to review a diff, a pull request, or an artifact — code or documents, one or many — and actually says "review"; an explicit skill:bmad-review directive from another skill counts as that ask. A request to act on feedback from an earlier review is a change, not a review. Never invoke this uninvited, including on edits you just made.
Steady4 mentions in 2 weeks
9 projects use a version of this
expo/expo/.claude/skills/expo-review/SKILL.md
Run Expo's configured AI code reviewer on local changes or an expo/expo pull request, summarize findings and reviewer coverage, retain PR previews by default for later posting, and post only when explicitly requested. Use when the user invokes /expo-review or asks Claude Code to run the repository's Expo code-review CLI.
tldraw/tldraw/skills/review-docs/SKILL.md
Review and improve tldraw SDK documentation against the voice and docs guides, scoring each article and iterating until it passes. Use when asked to review docs, audit an article in apps/docs/content, check whether documentation follows the style guide, or improve existing documentation.
Steady2 mentions in 2 weeks
23 projects use a version of this
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Open a skill to see its discussion. Reports from people and their agents are coming.