code-review
tachyon-zcash/ragu/.claude/skills/code-review/SKILL.md
Review Rust changes using Ragu policies; validate findings and report coverage.
Often used withclose-specadd-new-modelazsdk-common-apiview-feedback-resolution
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.
tachyon-zcash/ragu/.claude/skills/code-review/SKILL.md
Review Rust changes using Ragu policies; validate findings and report coverage.
Often used withclose-specadd-new-modelazsdk-common-apiview-feedback-resolution
lossless-claude/lcm/.agents/skills/code-review/SKILL.md
Review code changes in the lcm repository. Use when asked to review a PR, diff, or code change. Encodes project-specific rules for the SQLite daemon, connection lifecycle, type safety, performance gates, test coverage, transactions, migrations, and error handling.
Often used withclose-specadd-new-modelazsdk-common-apiview-feedback-resolution
leochiu-a/universal-agents/.agents/skills/code-review/SKILL.md
Skill: Code Review ## Purpose Provide concrete and actionable code-review feedback to surface bugs, risks, and testing gaps. ## Trigger conditions - Tasks that explicitly request a code review or quality audit
Often used withclose-specadd-new-modelazsdk-common-apiview-feedback-resolution
maxedapps/agent-skills/skills/code-review/SKILL.md
Reviews code changes and codebases for real defects and unnecessary complexity. Use this skill when asked to review a diff, branch, codebase, or completed implementation, or to check work against its plan. Do not use for an HTML walkthrough of a pull request (use pr-review) or for planning.
Often used withclose-specadd-new-modelazsdk-common-apiview-feedback-resolution
schmitthub/clawker/.github/skills/code-review/SKILL.md
Review a pull request in this repository. Use this when asked to review a pull request, a diff, or a branch.
Often used withclose-specadd-new-modelazsdk-common-apiview-feedback-resolution
block/proto-fleet/.github/skills/code-review/SKILL.md
Review Proto Fleet pull requests for concrete security, correctness, and reliability defects. Use for every GitHub Copilot code review.
Often used withclose-specadd-new-modelazsdk-common-apiview-feedback-resolution
LongNgn204/local-coding-agent/skills/code-review/SKILL.md
Review the current git diff for bugs, security issues, and clarity, then summarize findings by severity.
Often used withclose-specadd-new-modelazsdk-common-apiview-feedback-resolution
xin-lai/CodeSpirit/.cursor/skills/code-review/SKILL.md
基于 CodeSpirit 项目规范进行系统化代码审查。检查安全、数据库、异步编程、多语言、DTO、控制器、服务类等规范。当用户需要审查代码、检查代码质量、或准备提交代码时使用。
Often used withclose-specadd-new-modelazsdk-common-apiview-feedback-resolution
dzhng/duet-agent/.agents/skills/code-review/SKILL.md
Review changed code for naming, stale references, unnecessary complexity, and comment quality. Use after completing implementation work, before committing, or when the user asks to review or audit code.
194 projects use a version of this
Often used withclose-specadd-new-modelazsdk-common-apiview-feedback-resolution
elastic/cli/.github/skills/code-review/SKILL.md
Guidelines to apply when doing a code review on a pull request
Often used withclose-specadd-new-modelazsdk-common-apiview-feedback-resolution
alamops/skills/skills/code-review/SKILL.md
(alamops) Performs a thorough, read-only code review of any change source — a pull request, a git diff, uncommitted edits, recent commits, or code just produced in the conversation — and re-reviews a fix round, scoring each earlier finding fixed / partial / not fixed. Flags bugs; security and trust-boundary gaps (tenant isolation, authz, approvals bound to the wrong version, untrusted input driving privileged state, atomicity, retry safety, RLS self-recursion); reliability under the real deployment (two instances, crashes mid-step, network calls inside transactions, unbounded retries); code that is written and tested but never wired into production; PR-body and doc claims the code doesn't back; tests that cannot fail; performance, config and schema drift; and blast-radius gaps — checked against the repo's own rules and specs. Returns findings with severity, file:line, a failure scenario and a fix; never edits code. Use for any code review, PR review, re-review, diff review, or critique of recent changes.
Often used withclose-specadd-new-modelazsdk-common-apiview-feedback-resolution
martinffx/atelier/skills/code-review/SKILL.md
Multi-agent code review run as a debate. Critics raise findings in parallel, an Author defends the change, Critics concede or maintain, and a Judge rules on what stays contested. Findings are classified by kind and blocking, and handled durably when previously decided. Use `rq` to request a review of diffs (defaults to main branch), `rs` to respond to findings and record intentional non-fix decisions beside the relevant code. Triggers on "review this", "review my code", "code review", "check for bugs", "audit this", when examining PRs, pull requests, branches, or diffs. Always asks user before applying fixes or adding decision comments.
Often used withclose-specadd-new-modelazsdk-common-apiview-feedback-resolution
alexandru/skills/skills/engineering/code-review/SKILL.md
Reviews changed code using the shared code-reviewing workflow.
Often used withclose-specadd-new-modelazsdk-common-apiview-feedback-resolution
krishnakanthb13/antigravity_global_skills/code_review/SKILL.md
Comprehensive code review covering Functionality, Security (OWASP), Performance, and Maintainability. Includes good/bad examples.
larchanka/skills/code-review/SKILL.md
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
Often used withclose-specadd-new-modelazsdk-common-apiview-feedback-resolution
zvadaadam/az-skills/skills/engineering/code-review/SKILL.md
Multi-lens code review — spawns parallel sub-agents to independently review branch changes for bugs, security, and design, then validates and reports only high-signal findings. Use when you want a thorough review before merging or when self-reviewing your own changes.
Often used withclose-specadd-new-modelazsdk-common-apiview-feedback-resolution
drvoss/everything-copilot-cli/skills/development/code-review/SKILL.md
Use when reviewing code changes for quality, correctness, and security — runs a structured checklist with severity-rated findings
Often used withclose-specadd-new-modelazsdk-common-apiview-feedback-resolution
jezweb/vite-flare-starter/skills/code-review/SKILL.md
Review code for bugs, security issues, performance problems, and style. Use when the user pastes code, shares a file, or asks "what's wrong with this code?".
Often used withclose-specadd-new-modelazsdk-common-apiview-feedback-resolution
maragudk/skills/code-review/SKILL.md
Guide for making code reviews. Use this when asked to make code reviews, or ask to use it before committing changes.
Often used withclose-specadd-new-modelazsdk-common-apiview-feedback-resolution
microsoft/rego-cpp/.github/skills/code-review/SKILL.md
Perform a multi-perspective code review of rego-cpp changes. Use when: reviewing a release, auditing a branch diff, evaluating a PR, or performing a pre-merge code review. Launches four parallel constructive review subagents (Security, Performance, Usability, Conservative), synthesises findings, then runs a sequential adversarial gap-analysis pass. Verifies key findings, produces a unified report with severity-ranked findings and actionable remediation recommendations.
Often used withclose-specadd-new-modelazsdk-common-apiview-feedback-resolution
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.