code-review
modimihir07/agentic-os/skills/code-review/SKILL.md
Automated code review with checklist and quality gates
Often used withclose-specadd-new-modelcompare-screenshots
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.
modimihir07/agentic-os/skills/code-review/SKILL.md
Automated code review with checklist and quality gates
Often used withclose-specadd-new-modelcompare-screenshots
Azure/azure-sdk-for-cpp/.github/skills/code-review/SKILL.md
Review Azure SDK for C++ pull requests for actionable regressions and C++ SDK API or implementation guideline violations. Use for GitHub Copilot Code Review (CCR) of SDK code and its related tests, CMake files, samples, and documentation.
Often used withclose-specadd-new-modelcompare-screenshots
coderabbitai/skills/skills/code-review/SKILL.md
Run CodeRabbit CLI reviews, retrieve saved local or GitHub PR fix prompts, and interpret CodeRabbit authentication and review output. Use for CodeRabbit review commands, committed/uncommitted or directory scopes, and CodeRabbit runbooks. Default code-review skill: also trigger for explicit code/PR/quality/security review requests or when a review is needed.
Often used withclose-specadd-new-modelcompare-screenshots
microsoft/aspire.dev/.agents/skills/code-review/SKILL.md
Reviews new or changed CODE on aspire.dev for correctness, safety, and adequate test coverage — not documentation prose. USE FOR: reviewing a PR supplied as a number or URL (or the current branch's diff), checking C#/TypeScript/Astro/HTML/CSS changes for bugs, catching correctness/security/data-loss/accessibility regressions, verifying that important scenarios have unit tests, e2e tests (desktop/tablet/mobile), and axe-core accessibility tests. DO NOT USE FOR: validating documentation content or examples (use doc-tester), reviewing a documentation PR for factual accuracy (use doc-pr-reviewer), writing or fixing docs pages (use doc-writer), two-slash TypeScript blocks (use twoslash-validator), or nitpicking style/formatting (ESLint and Prettier own that). INVOKES: git (read-only diff inspection), gh (to resolve and fetch a PR by number or URL), and optionally the repo's existing test commands for verification. FOR SINGLE OPERATIONS: read the diff with git or gh pr diff and apply the relevant language checklist directly.
Often used withclose-specadd-new-modelcompare-screenshots
microsoft/dcp/.agents/skills/code-review/SKILL.md
Review a GitHub pull request for problems and consistency with project conventions. Use when asked to review a PR, do a code review, check a PR for issues, or review pull request changes.
Often used withclose-specadd-new-modelcompare-screenshots
DerekYRC/mini-claude-code/skills/code-review/SKILL.md
Review code changes and report concrete risks first.
Often used withclose-specadd-new-modelcompare-screenshots
InternationalColorConsortium/iccDEV/.github/skills/code-review/SKILL.md
Review pull requests with changed-line evidence, repository-specific instructions, and minimal actionable findings.
Often used withclose-specadd-new-modelcompare-screenshots
microsoft/oxidizer/.github/skills/code-review/SKILL.md
Review guidance for pull requests in this repository. Use when reviewing a pull request, to keep comments on evidence you can see rather than on predicted build outcomes, remembered API signatures, or assumed conventions.
Often used withclose-specadd-new-modelcompare-screenshots
timlaing/pyicloud/.github/skills/code-review/SKILL.md
Use when reviewing code changes, PRs, or commits in the pyicloud project. Covers architecture, typing, service conventions, linting, test coverage, and SonarQube quality rules. Trigger keywords: review, pr, code review, linting, typing, coverage, sonarqube, prek.
Often used withclose-specadd-new-modelcompare-screenshots
holon-run/holon/skills/code-review/SKILL.md
Review a set of code changes using evidence-backed findings, explicit confidence, and a clear coverage summary.
Often used withclose-specadd-new-modelcompare-screenshots
maotoumao/Cebian/.agents/skills/code-review/SKILL.md
Use when completing a coding task to perform senior-level code review. Triggers on: code review, post-task review, review changes, check code quality, review my code.
Often used withclose-specadd-new-modelcompare-screenshots
maotoumao/Cebian/.claude/skills/code-review/SKILL.md
Use when completing a coding task to perform senior-level code review. Triggers on: code review, post-task review, review changes, check code quality, review my code.
Often used withclose-specadd-new-modelcompare-screenshots
maotoumao/Cebian/.github/skills/code-review/SKILL.md
Use when completing a coding task to perform senior-level code review. Triggers on: code review, post-task review, review changes, check code quality, review my code.
Often used withclose-specadd-new-modelcompare-screenshots
RedWoodOG/Hermes-Desktop/skills/claude-code/code-review/SKILL.md
Thorough code review with security, performance, correctness, and maintainability checks.
Often used withclose-specadd-new-modelcompare-screenshots
oaslananka/kicad-mcp-pro/.github/skills/code-review/SKILL.md
Use this skill for GitHub Copilot pull request and code reviews in oaslananka/kicad-mcp-pro. Review Python MCP server changes, KiCad adapter and tool-contract changes, tests, npm/package wrappers, Tauri/Rust desktop code, GitHub Actions, security controls, documentation, generated metadata, and compatibility/release surfaces. Use it whenever reviewing a PR or diff in this repository, especially changes under src/, tests/, packages/, src-tauri/, .github/workflows/, or public MCP metadata/configuration.
Often used withclose-specadd-new-modelcompare-screenshots
colasama/MahoShojo-Generator/.agents/skills/code-review/SKILL.md
Use when reviewing MahoShojo-Generator code, a branch, commit range, pull request, or implementation against current behavior and accepted ADR/spec requirements. Do not use when the primary request is to implement a known fix.
Often used withclose-specadd-new-modelcompare-screenshots
OpenHands/extensions/skills/code-review/SKILL.md
Review code changes for material correctness, security, compatibility, and maintainability risks, grounded in the current repository and acceptance criteria.
Often used withclose-specadd-new-modelcompare-screenshots
sammcj/agentic-coding/Skills/code-review/SKILL.md
Use when the user asks for a code review of a change, branch or PR.
Often used withclose-specadd-new-modelcompare-screenshots
totvs/engpro-advpl-tlpp-skills/skills/advpl-tlpp/code-review/SKILL.md
Perform comprehensive AdvPL/TLPP code review covering SonarQube rules, Protheus.doc documentation, security, performance, clean code, and TOTVS Protheus framework best practices. Use when a user says "review this code", "code review", "check this source", "audit this AdvPL/TLPP", or needs a structured quality assessment of .prw/.tlpp/.prx files.
Often used withclose-specadd-new-modelcompare-screenshots
HybridAIOne/hybridclaw/skills/code-review/SKILL.md
Review diffs and change sets for bugs, regressions, risks, and missing tests.
Often used withclose-specadd-new-modelcompare-screenshots
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.