Use only for reviewing completed Biome PRs, branches, commit ranges, diffs, or working trees against business logic and requirements. Excludes broad code-quality and process audits, triage, reproduction, and implementation.
26k10d agoReviewMountCreate a free account to mount
Review or re-review Scapy pull requests, branches, patches, and protocol implementations for correctness, simplicity, Scapy-likeness, backwards compatibility, robustness, performance, and tests. Compare old and new code, trace prior human review comments to their subsequent fixes, and return concise, evidence-backed, actionable findings rather than speculative suggestions.
Steady8 mentions in 2 weeks
No other project uses it yet
13k5y agoReviewMountCreate a free account to mount
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
Review a Polar branch diff against conventions, Accepted ADRs, reuse, slop, and path-triggered API, ship-safety, and billing lenses. Use before opening a PR, when the user asks for a Polar code review, /polar-code-review, or $polar-code-review. Not a bug hunt or security review.
Steady2 mentions in 2 weeks
No other project uses it yet
10k9d agoReviewMountCreate a free account to mount
Use only when the user explicitly requests a review or audit of backend code under `api/`. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for implementation-only requests, diagnosis without review intent, frontend code, or backend code outside `api/`.
6 projects use a version of this
161k16d agoReviewMountCreate a free account to mount
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `src/backend/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.
6 projects use a version of this
156k20d agoReviewMountCreate a free account to mount
The code review workflow for this Gradle repository. Use whenever the user asks to review code, perform/do a code review, review a change, diff, branch, or PR, or check changes before they reach the target branch. Prefer this over any generic code-review skill when working in this repo.
19k18d agoReviewMountCreate a free account to mount
Code review criteria — the five review axes, core principles, severity format, and verdict for reviewing code changes. Loaded by the reviewer subagent of the review-code flow. Not a user-facing flow — to review code, use the review-code flow.
Steady6 mentions in 2 weeks
No other project uses it yet
62k2mo agoReviewMountCreate a free account to mount
Reviews code changes for reuse, composition, codebase consistency, and slop. Use when asked to review PRs/diffs, check code reuse, composition, cleanliness, or whether code fits the codebase.
3 projects use a version of this
12k3mo agoReviewMountCreate a free account to mount
Review pull requests for copy-paste defects and accidentally committed sensitive data. Use this during code review when changed code may have been copied or pasted.
Steady6 mentions in 2 weeks
No other project uses it yet
52k2mo agoReviewMountCreate a free account to mount
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.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
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.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.