Review changed code against repository coding standards and original specification intent. Use when reviewing a branch, diff, PR, pull request, merge-base changes, or verifying code against documented standards — even if the user just says \"review this\". Do NOT use for authoring new code or diagnosing failing runtime bugs.
Performs an architectural and quality code review on a specified file or set of files. Checks for coding standard compliance, architectural pattern adherence, SOLID principles, testability, and performance concerns.
Systematic code review and static analysis directive. Validates vulnerability thresholds, architectural patterns, and production reliability via automated CI/CD security constraints.
Review a diff or PR against my conventions — Result not throw, vertical slices, AItError codes, node:test, Biome, entity normalisation, a11y. Findings are triaged by severity (correctness → conventions → polish), not piled in a flat list. Use when reviewing a diff, reviewing a PR before merge, self-reviewing before opening a PR, or when user says "review this", "review the diff", "code review", or invokes `/code-review`.
Runs one adaptive multi-agent code review of a PR, commit, or the whole codebase. Always covers six core dimensions (correctness, performance, code style, test coverage, error handling, simplicity/over-engineering) plus architecture and design patterns, then adds security, dependency, deep-performance, and UI/motion lanes when the change touches those areas. Critical and Major findings are adversarially verified before the severity-ranked report with file:line findings and fixes goes out in chat. Use when the user wants a thorough review, asks to review a PR or diff, or wants over-engineered code flagged. Analysis only: never edits code, commits, or applies fixes, and posts to GitHub only when explicitly asked. Not for a standalone security audit (use review-security), a standalone dependency audit (use review-deps), a standalone performance investigation (use review-perf), or a standalone UX/design critique (use review-design).
Use when the user asks for a code review, architecture review, Go review, Go best practices review, protobuf review, proto or API design review, SOLID review, design pattern review, package design review, coupling or cohesion review, testability review, "review this code", "is this well designed", "is this idiomatic Go", a gocyclo or staticcheck pass, or a buf lint run. Also use when another skill dispatches a code review.
Review one implementation change against its Phat task, feature spec, acceptance criteria, repository engineering standards, and any accepted prototype evidence. In standalone or final mode record supported task evidence/status; in delegated mode return a read-only report to the parent. Use after implement-task or when reviewing a working tree, staged change, commit, or branch.
code-review
Use this skill when the task is a codereview rather than feature implementation.
Focus on:
- correctness bugs
- regressions
- missing tests
- risky assumptions
Return findings first.
Keep
Comprehensive code review with distinct aspect based sections. Use when reviewing code, checking for security issues, finding type safety problems, auditing code quality, or when user asks to review code, PRs or changes. Three-phase workflow runs static tools, LLM judgment, and writes diagnostic log.
Automated code review for pull requests and code changes using multi-agent architecture with confidence-based scoring. Use when reviewing PRs, auditing code changes, checking guideline compliance, or detecting bugs in diffs. Works with GitHub, GitLab, and local git repositories. Compatible with Claude Code, Codex, Cursor, Windsurf, and other AI coding tools.
Perform automated code reviews with best practices, security checks, and refactoring suggestions. Use when reviewing code, checking for vulnerabilities, or analyzing code quality.
Use when receiving code review feedback (especially if unclear or technically questionable), when completing tasks or major features requiring review before proceeding, or before making any completion/success claims. Covers four practices — receiving feedback with technical rigor, requesting reviews via code-reviewer subagent, verification gates requiring evidence before claims, and security/API-compat awareness. Essential for subagent-driven development, pull requests, and preventing false completion claims.
Review a source-code diff, PR, or file against canonical review criteria — Fowler code smells with named refactorings, Clean Code / A Philosophy of Software Design red flags, error-handling/resource-safety gaps, testability seams and test smells, security/secrets basics, performance basics, plus concurrency, database/N+1, distributed-systems, API-contract, observability modules — each defect reported as a line-anchored finding with a named fix. Invoke when asked to review code, a diff, or a PR for quality, maintainability, or correctness, or to find code smells and refactoring opportunities in ordinary application source. Skip when the target is a GitHub Actions workflow (use audit-github-actions-security), a SKILL.md (use audit-skill-quality), an agent instruction file (use audit-instruction-file), an agent harness's security/data-flow architecture (use audit-lethal-trifecta) or its LLM-output sinks/install authority (use audit-supply-chain-sinks), or when writing new tests from a spec (use write-tests).
Review any ECorp pull request against its PR-template merge-readiness rubric, ATV security, Ponytail complexity audit, and Santa verification. Use for automatic Copilot PR reviews, explicit open-PR sweeps, and explicitly authorized TDD remediation with issue-scoped subagents.
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.