Perform thorough code reviews with security, performance, and maintainability analysis. Use when user asks to review code, check for bugs, or audit a codebase.
Perform code review. Use for: (1) '/code-review' to review the current branch changes, (2) '/code-review PR #123' to review a specific PR, (3) '/code-review staged' to review staged changes, (4) requests such as 'review this code' or 'please review'.
Skill: Structured CodeReview
## Role
You are a Senior CodeReviewer specializing in architectural integrity, idiomatic patterns, and security.
## Objective
Provide high-signal, actionable feedback on code changes, prioritizing architectural
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/PRD 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".
Use when the user wants to review a file for bugs, antipatterns, or quality issues. Triggers on "review", "check for issues", "look for problems", "audit", "before I ship".
Evidence-based review of pull requests, branch comparisons, working-tree changes, or selected code across risk, repository standards, and originating requirements. Use when asked to review code, a PR, changes since a fixed point, or to coordinate an explicitly authorized review → repair → verify loop. Defaults to read-only.
Review code changes for correctness, conventions, performance, security, and test coverage. Use for: PR review, regression-risk analysis, Biome/TypeScript convention checks, API auth and validation review, block/tool contract audits, and severity-ordered findings.
Review code changes for correctness defects, regressions, security risks, data-integrity problems, concurrency hazards, and missing meaningful tests. Use for pull requests, branches, commits, patches, or working-tree reviews; do not use for implementation unless the user separately requests fixes.
153mo agoReviewMountCreate a free account to mount
Revisão holística pré-commit (estilo PR Review). Valida o diff contra as 3 memórias vivas, a spec da task e Clean Code, em paralelo ao QA/Security (fan-out); a evidência de teste é exigida no join. Executada pelo Tech Lead; veredito escrito em review.md.
Reviews a git diff (working-tree changes, a commit range, or an explicitly named PR/branch/file) for correctness bugs and code-quality issues -- wrong conditions, removed invariants, broken call sites, duplicated logic, unnecessary complexity, wasted work, fixes at the wrong depth, and convention violations -- using eight independent review angles, a one-pass verification step per candidate, and a capped, severity-ranked report. Also reviews a remote merge request on a hosted platform (through that platform's own skill, e.g. `glab` for GitLab) and, only when asked, posts the findings back as comments. Use when the user asks to review code, review a PR/MR, review this diff, or check recent changes for bugs before merging.
Review pull requests in the SAP Testing Automation Framework. Use when reviewing a diff, a pull request, or staged changes touching platform code, Ansible roles and playbooks, custom modules, or the shell CLI. Reviews for correctness, reliability, security, Azure/SAP domain rules, performance, test coverage, and maintainability — in that priority order. Finds defects that let a validation report success without validating, accept a field and then discard it before it acts, break an object's stated contract, or leave one half of the SUSE/RHEL or HANA topology matrix unhandled.
Review diffs, commit ranges, fixup chains, or PRs across languages and report findings ordered by severity. Enforces primitive-obsession and smart-constructor blockers, property-test and boundary-test requirements, complexity thresholds and per-language rules (Rust, TypeScript, Lean, SQL, bash, Ruby, Markdown, regex). Delegates commit-history structure and repair to git-review. Also the home for changing review rules or codifying review feedback.
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\".
Review GitCode pull requests with a self-contained multi-agent prompt pipeline, validate JSON review findings, post or delete GitCode inline comments, and create/update GitCode PR metadata with this skill's scripts.
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.