Claude skills and agent skills

ElasticSkill

code-review

elastic/cli/.github/skills/code-review/SKILL.md

Guidelines to apply when doing a code review on a pull request

Often used withclose-spec·add-new-model·compare-screenshots

alamopsSkill

code-review

alamops/skills/skills/code-review/SKILL.md

(alamops) Performs a thorough, read-only code review on any source of changes — a pull request, a git diff, uncommitted edits in the working tree, recent commits on the current branch, or code that was just produced or discussed in the conversation. Flags bugs, security issues (tenant isolation, authz gaps, atomicity, retry safety, multi-step flow completeness, RLS / row-policy self-recursion), performance issues (in-memory aggregation, sequential fan-out, partial-period comparisons), consistency issues (including schema ↔ code column-reference drift), and blast-radius gaps. Returns structured findings (category, severity, file, line, suggestion) without modifying any code. Use whenever the user asks for a code review, PR review, diff review, feedback on pending or recent changes, or a critique of code just written in this session.

Often used withclose-spec·add-new-model·compare-screenshots

alexandruSkill

code-review

alexandru/skills/skills/engineering/code-review/SKILL.md

Reviews changed code using the shared code-reviewing workflow.

Often used withclose-spec·add-new-model·compare-screenshots

krishnakanthb13Reads credentialsSkill

code_review

krishnakanthb13/antigravity_global_skills/code_review/SKILL.md

Comprehensive code review covering Functionality, Security (OWASP), Performance, and Maintainability. Includes good/bad examples.

renzrollonSkill

review-code

renzrollon/interlock/skills/review-code/SKILL.md

Adversarially verified multi-dimensional review of a code diff. Runs independent reviewers across language, architecture, QA, technical-lead and regression, the review depth deciding which of them always run, plus devops, security, domain and blast radius (who outside the diff observes the change, from the codebase graph) only when the diff calls for them, then makes two skeptics try to refute every blocker and warning before it reaches you. Use after implementing a change, before opening a PR, or when a diff is high-stakes enough that false positives would waste real time.

zvadaadamSkill

code-review

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-spec·add-new-model·compare-screenshots

drvossSkill

code-review

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-spec·add-new-model·compare-screenshots

jezwebSkill

code-review

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-spec·add-new-model·compare-screenshots

maragudkSkill

code-review

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-spec·add-new-model·compare-screenshots

martinffxSkill

code-review

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-spec·add-new-model·compare-screenshots

MicrosoftSkill

code-review

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-spec·add-new-model·compare-screenshots

salavenderSkill

code-review

salavender/antigravity-compound-engineering-plugin/skills/code-review/SKILL.md

Systematic multi-perspective code review with consistent quality gates.

Often used withclose-spec·add-new-model·compare-screenshots

ZhangHanDongReads credentialsSkill

code-review

ZhangHanDong/cowork-skills/skills/code-review/SKILL.md

CRITICAL: Code review skill using GitHub API. Triggers on: review PR, code review, PR review, pull request review, review changes, check this PR, analyze this PR, review #, 代码审查, 审查 PR

Often used withclose-spec·add-new-model·compare-screenshots

iliaalSkill

code-review

iliaal/ai-skills/skills/code-review/SKILL.md

Structured code reviews with severity-ranked findings and deep multi-agent mode. Use when performing a code review, auditing code quality, or critiquing PRs, MRs, or diffs, including a diff or patch pasted inline. For the full multi-agent workflow, use the ia-review command (/ia-review in Claude Code).

Often used withclose-spec·add-new-model·compare-screenshots

zhao-wuyanSkill

review-code

zhao-wuyan/ccw-command-explorer/.claude/skills/review-code/SKILL.md

Multi-dimensional code review with structured reports. Analyzes correctness, readability, performance, security, testing, and architecture. Triggers on "review code", "code review", "审查代码", "代码审查".

addxaiSkill

code-review

addxai/enterprise-harness-engineering/skills/code-review/SKILL.md

Use when reviewing code changes — MR/PR review, local commits, or uncommitted changes. Reviews document compliance, content quality (architecture soundness, test completeness, observability coverage), and end-to-end consistency (User Story ↔ design ↔ code ↔ tests ↔ observability). Triggers on "review MR", "review this commit", "review my changes", "code review", "help me review".

Often used withclose-spec·add-new-model·compare-screenshots

FTShare-LabSkill

code-review

FTShare-Lab/agent-claim-network/.agents/skills/code-review/SKILL.md

Multi-pass code review. Review changes locally, then run `codex exec --json` as an independent read-only reviewer and merge the findings. Use before merging or after significant refactoring.

Often used withclose-spec·add-new-model·compare-screenshots

FTShare-LabSkill

code-review

FTShare-Lab/agent-claim-network/.claude/skills/code-review/SKILL.md

Run ACN's canonical local-plus-external code-review workflow before merging or after significant refactoring.

Often used withclose-spec·add-new-model·compare-screenshots

NVIDIASkill

review-code

NVIDIA/OpenShell-Research/projects/tools/openshell-agent-runner/src/openshell_agent_runner/profiles/code-reviewer/skills/review-code/SKILL.md

Review a code repository for concrete issues in correctness, robustness, security, maintainability, tests, and integration. Use for repository-wide or focused code review where practical engineering judgment and strict scope control matter.

romiluz13Skill

code-review

romiluz13/mifal/skills/code-review/SKILL.md

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".

Often used withclose-spec·add-new-model·compare-screenshots