Find the best CLAUDE.md, AGENTS.md and Claude skills

static-web-serverSkill

pr-review

static-web-server/static-web-server/.agents/skills/pr-review/SKILL.md

Review a pull request for the Static Web Server (SWS) project — a standard PR (bug fix, feature, refactor, docs) or an advisory PR (security fix in a GHSA private fork). Reproduce and verify locally, review adversarially, check PR hygiene, then leave concise, evidence-backed inline comments as a pending (draft) GitHub review via gh.

levy-streetSkill

review-pr

levy-street/world-of-claudecraft/.claude/skills/review-pr/SKILL.md

Review a GitHub pull request for World of ClaudeCraft the way the maintainer does. Use when asked to review a PR, look at a PR, or check a PR (a github.com/.../pull/<n> link or a PR number). Fetches the PR, classifies the change by domain (sim, wire/parity, render, ui, server, i18n), verifies the repo's invariants against the real code (not the PR description), checks the merge-conflict scope, independently confirms any consequential finding, then posts a short, plain, friendly GitHub review with severity-tagged findings. Not for reviewing the local working tree (that is /code-review).

NVIDIA-NeMoSkill

pr-review

NVIDIA-NeMo/Nemotron/skills/pr-review/SKILL.md

Review Nemotron pull requests for code correctness, instructions that match the implementation, first-user setup, and reproducible notebooks and cookbooks.

mampfesSkill

review-pr

mampfes/hacs_waste_collection_schedule/.agents/skills/review-pr/SKILL.md

Review a pull request for hacs_waste_collection_schedule and execute only approved fixes or review actions. Use when the user asks to inspect, fix, approve, or request changes on a PR.

EpicGamesSkill

review-change

EpicGames/lore/.claude/skills/review-change/SKILL.md

Must be used before submitting any change to Lore, and to review another author's change. Reviews the change adversarially, in a fresh session, against code-review.md and the standards it names. On your own branch it fixes the findings that have one obvious fix and reports the rest; on another author's change it reports the findings by severity.

Often used withplan-change·implement-change

kubeflowSkill

review-pr

kubeflow/trainer/.agents/skills/review-pr/SKILL.md

Comprehensive PR review using specialized agents. Use when asked to review a pull request or local changes before committing or creating a PR.

storybookjsSkill

docs-review

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.

openmc-devSkill

reviewing-openmc-code

openmc-dev/openmc/.claude/skills/reviewing-openmc-code/SKILL.md

Reviews code changes in the OpenMC codebase against OpenMC's contribution criteria (correctness, testing, physics soundness, style, design, performance, docs, dependencies). Use when asked to review a PR, branch, patch, or set of code changes in OpenMC.

arjun988Skill

qa-review

arjun988/blender-skills/.claude/skills/qa-review/SKILL.md

Production QA gate for Blender assets using viewport screenshots, validation checklists, naming audits, and ship/no-ship verdicts via MCP.

ShenSeanChenReads credentialsSkill

review-pr

ShenSeanChen/waku-agent/.claude/skills/review-pr/SKILL.md

Walk Sean through an incoming waku-agent PR or issue and present it his way — four fixed sections: what this is, why it matters, how HE can test it with you as copilot, and are we ready to merge / reply / close and why. Use whenever Sean asks to look at, test, triage, or decide on a pull request or an issue, and whenever a queue of them is being drained one at a time.

isairSkill

review-pr

isair/jarvis/.agents/skills/review-pr/SKILL.md

Single-pass PR review for code quality, maintainability and simplicity, potential issues, CI failures, test coverage, and adherence to project standards. Lighter than `/review-pr-ultra`. Use for routine reviews; use `/review-pr-ultra` for high-risk, security-sensitive, or large changes where deeper multi-agent analysis is warranted.

authgearSkill

review-pr

authgear/authgear-server/.claude/skills/review-pr/SKILL.md

Produce a structured code review report for the current branch's PR (purpose, API interface changes, code quality, bugs, behavior changes, security, performance), with a mandatory second verification pass. Use when the user asks "what does this PR do", "review this branch/PR", or asks to confirm/double-check review findings and look for more issues.

lobehubSkill

deep-review

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.

NVIDIA-NeMoSkill

review-pr

NVIDIA-NeMo/RL/skills/review-pr/SKILL.md

Interactive code review for NVIDIA-NeMo/RL pull requests. Checks out PR locally, reads existing comments, applies coding guidelines from skills, previews findings, and posts review comments. Also supports reviewing the current branch locally.

jaemkSkill

pr-review

jaemk/cached/.agents/skills/pr-review/SKILL.md

Targeted, read-only review of a PR or checked-out branch. Acquires the diff (a PR number, or the current branch vs origin/master), shards the changed material into appropriately sized, randomized chunks, and spawns multiple read-only code-review and library-consumer sub-agents in parallel (one per shard), then aggregates and de-duplicates their findings into a single report with severity and a valid / already-fixed / invalid verdict for each. Read-only — it does not edit files, commit, push, or touch the GitHub PR conversation. The review sub-agents default to Sonnet but can be overridden per run (e.g. to opus). Use when asked to "review this PR", "review the branch", "what's wrong with this diff", "do a code review", or "review with opus". For the full review → fix → push → resolve loop, use `pr-cycle` (which delegates its review step here).

zerx-labSkill

review-pr

zerx-lab/warp/.agents/skills/review-pr/SKILL.md

Review a pull request diff and write structured feedback to review.json for the workflow to publish. Use when reviewing a checked-out PR from local artifacts like pr_diff.txt and pr_description.txt and producing machine-readable review output instead of posting directly to GitHub.