Review a Fleet pull request for correctness, Go idioms, SQL safety, test coverage, and conventions. Use when asked to "review PR" or "review pull request".
Steady8 mentions in 2 weeks
185 projects use a version of this
7.2k7mo agoReviewMountCreate a free account to mount
Extremely strict structural review of a Kev branch or PR (code-judo simplifications, spaghetti growth, files past 1k lines, boundaries, duplication of canonical helpers). Use when asked to review a PR, audit a diff, or run a "thermonuclear" or deep code quality review on this repo.
No other project uses it yet
9.8k37d agoReviewMountCreate a free account to mount
Use whenever the user asks to review, vet, or sanity-check a pull request, or to act on the review comments already on one — a GitHub PR URL pasted with little or no instruction, a bare PR number, "review this PR", "is this PR safe", "can I merge this", "check this contribution", "any issues with #1234", "check the bot comments", "fix the CodeRabbit findings", "address the review comments", "update the PR if required". Runs the standing SparkyFitness review: supply-chain, phishing and code-provenance checks first, then architecture alignment with AGENTS.md and agent-docs, then logic, then the state of existing review-bot and reviewer threads. Reports to the terminal only.
196 projects use a version of this
6.7k17d agoReviewMountCreate a free account to mount
Use whenever the user asks to review, vet, or sanity-check a pull request, or to act on the review comments already on one — a GitHub PR URL pasted with little or no instruction, a bare PR number, "review this PR", "is this PR safe", "can I merge this", "check this contribution", "any issues with #1234", "check the bot comments", "fix the CodeRabbit findings", "address the review comments", "update the PR if required". Runs the standing SparkyFitness review: supply-chain, phishing and code-provenance checks first, then architecture alignment with AGENTS.md and agent-docs, then logic, then the state of existing review-bot and reviewer threads. Reports to the terminal only.
196 projects use a version of this
6.7k17d agoReviewMountCreate a free account to mount
Verify the technical accuracy of a vscode-docs pull request against the VS Code source code in microsoft/vscode. Use when reviewing a docs PR for factual correctness: setting names, command IDs, default values, API shapes, keybindings, versioned availability, and described behavior.
6.7k9mo agoReviewMountCreate a free account to mount
Review a Baserow pull request, branch, or diff against its actual base the way the maintainers do. Use when asked to review, deeply review, re-review, or triage review comments on a PR, including follow-up rounds on the same PR.
6.3k30d agoReviewMountCreate a free account to mount
Review a Dograh pull request, branch diff, or pasted patch for repo-specific security and correctness risks that are not obvious from generic FastAPI, Next.js, or Python conventions. Use when the user asks to review a PR, audit a diff, check whether changes are safe to merge, review their own changes, or asks what to look for in a Dograh PR. Focus on tenant isolation, route auth, webhook signing and org derivation, DB layering, worker-sync, migrations, generated SDK usage, and test hazards.
6k2mo agoReviewMountCreate a free account to mount
Review torchtitan pull requests the way the maintainers do -- question the problem and design first, push for minimal code, explain the change with a concrete example, then check correctness. Use when reviewing a PR or branch, when asked to "review", "review again", "review my review", or to evaluate a maintainer's comments.
Steady2 mentions in 2 weeks
195 projects use a version of this
5.9k11d agoReviewMountCreate a free account to mount
Author and file a separate ASP.NET Core API review issue from an originating issue and an implementation pull request or commits. USE FOR writing API review issues, preparing api-ready-for-review proposals, filling API proposal templates, creating API review descriptions from issues and code changes, "fill out the API review", "prepare API review", or opening a pull request that changes public API. DO NOT USE FOR reviewing API design decisions, approving APIs, implementing APIs, or general code review.
39k6mo agoReviewMountCreate a free account to mount
Reviews an RLinf pull request for correctness, design, code reuse, tests, and docs against RLinf's code and design patterns and the docs style guide, reports the findings in a fixed format, and, after asking, posts them as one GitHub review with a main comment that answers the review questions and inline comments with suggested fixes. Use when the user asks to review a PR, check a PR before merge, or post review comments.
5.6k10d agoReviewMountCreate a free account to mount
Review pending UTM changes before they are submitted. Runs a standard correctness/quality code review of the current branch's diff AND audits it against UTM's contribution rules in CONTRIBUTING.md and AGENTS.md — scope discipline, commit/PR format, AI attribution, logging hooks, generated files, UI/design philosophy, and platform compatibility. Use this before opening or updating a UTM pull request, whenever the user asks to review UTM changes, or when the user runs /utm-review. The /utm-submit workflow expects this to have been run on the current changes first.
37k8d agoReviewMountCreate a free account to mount
Review an OpenMetadata connector against golden standards. Runs multi-agent analysis covering architecture, code quality, type safety, testing, and performance. When a PR number is given, automatically posts the quality summary to the PR description and a detailed review as a PR comment.
Steady4 mentions in 2 weeks
1 project uses a version of this
16k36d 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.