Use for source-read-only review of a PR, diff, commit, migration, refactor, or implementation through its dependency cone. Not for root-cause diagnosis, authorised fixes, or browser/UX review; use diagnose, implement, or ui-ux-design.
Code review practices and pull request quality standards. Use when: reviewing a pull request, preparing code for review, writing review comments, checking for common issues, establishing review guidelines, auditing an existing project's review practices, or improving PR quality standards. Integrates linting, testing, security, and CI/CD checks into a cohesive review workflow.
Review code for actionable defects. Correctness is the core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary, forces a violating execution, and refutes every candidate before reporting. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.
Review code changes, diffs, outstanding changes, or modified files. Use when asked to review, check, or analyze code quality, changes, uncommitted work, or changes since diverging from a branch (e.g., main).
Code review a pull request, commit, file, or local git changes. Use when the user says "review", "code review", "/code-review", "review local changes", "review PR", "review commit", or asks for a review of changes.
Review implemented changes for completeness, correctness, simplification, security, quality, tests, performance, and documentation. Use for branch, pull-request, staged, or worktree reviews after a fixed comparison point is known.
Clean up code comments, then review code with comprehensive and quick modes. Use when reviewing code changes, PRs, or specific files for quality, bugs, and best practices.
Select and perform risk-appropriate Quick, Code, Architecture, Security, Performance, or Integration Review on a concrete revision. Use after implementation or integration to assess whether the solution is reasonable, maintainable, compliant, and safe.
Reviews code for quality, best practices, and potential issues. Use when reviewing pull requests, checking code quality, or when the user asks for code review.
Structured engineering code review covering readability, complexity, test gaps, SOLID principles, and API consistency. Complements full-security-review with general code quality.
review, code review, review code, review changes, diff review, patch review, pr review, 代码评审, 代码审查, 变更评审, PR评审. Use when evaluating code changes against repository requirements and engineering rules, and when a structured review report with findings and compliance status is needed.
Review HR-ERP PRs as a T0-T4 agent-governance scaffold, not a payroll product. Use on pull requests that touch Prisma, RLS, payroll fixtures, governance lint, or Next.js app routes. Flag real PII, Cedar duplication, and demo-signin on production.
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.