code-review
/code-review
Review code for quality, bugs, and design issues. Use when the user says "review this code", "do a code review", "check this PR", "review this diff", "is this code good", "what's wrong with this code", "code quality check", or pastes code and wants feedback - even if they don't explicitly say "code review".
- Author
- qa-aman ↗
- Repository
- claude-skills ↗
- Licence
- MIT
- Last repository change
- 19.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 19.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Review code for quality, bugs, and design issues. Use when the user says "review this code", "do a code review", "check this PR", "review this diff", "is this code good", "what's wrong with this code", "code quality check", or pastes code and wants feedback - even if they don't explicitly say "code review".
Triggers from the description
Original author description
Review code for quality, bugs, and design issues. Use when the user says "review this code", "do a code review", "check this PR", "review this diff", "is this code good", "what's wrong with this code", "code quality check", or pastes code and wants feedback - even if they don't explicitly say "code review".
How it works
- Overview
- Workflow
- Anti-Patterns
- Quality Checklist
SKILL.md preview
--- name: code-review description: > Review code for quality, bugs, and design issues. Use when the user says "review this code", "do a code review", "check this PR", "review this diff", "is this code good", "what's wrong with this code", "code quality check", or pastes code and wants feedback - even if they don't explicitly say "code review". --- ## Overview Based on **"Clean Code"** by Robert C. Martin. Martin's central argument: code is read far more than it is written. Clean code reads like well-written prose - the reader can understand the intent without decoding it. A code review is not just a bug hunt - it's a check that the code communicates its intent clearly to the next developer who reads it. ## Workflow ### Step 1: Read for intent first Before looking for bugs, read the code as a whole. Can you understand what it does without reading comments or documentation? If not, that's the first finding. ### Step 2: Check naming Martin's rule: names should reveal intent. Review every variable, function, and class name. - Does the name tell you what it does, not how it does it? - Would a new team member understand this name without context? - Are booleans named as predicates? (`isValid`, `hasPermission`, not `flag`, `check`) Bad: `d = datetime.now() - start` Good: `elapsed_time = datetime.now() - start` ### Step 3: Check function size and responsibility Martin's single responsibility principle: a function should do one thing and do it well. - Functions longer than 20 lines are candidates for extraction - If a function needs a comment to explain what each section does, split it - If a function has multiple levels of abstraction mixed together, extract ### Step 4: Check error handling - Are errors handled explicitly or silently swallowed? - Do error messages help the caller understand what went wrong and how to fix it? - Are exceptions used for exceptional cases only - not flow control? ### Step 5: Check for duplication Martin's DRY principle: duplication is the root of all evil in software. - Is this logic duplicated elsewhere in the codebase? - Could this be extracted to a shared utility? - Are magic numbers duplicated? (extract to named constants) ### Step 6: Check tests - Are there tests for the new or changed behavior? - Do tests cover the happy path AND failure cases? - Are test names descriptive? (`test_login_fails_with_invalid_password` not `test_login_2`) ### Step 7: Write the review Structure feedback as: - **Must fix** - bugs, security issues, broken contracts - **Should fix** - Clean Code violations that will cause maintenance pain - **Consider** - style suggestions, optional improvements - **Praise** - what was done well (important for team morale and learning) ## Anti-Patterns **1. Nitpicking style without flagging real issues** Bad: 10 comments about variable naming, zero comments about a missing null check. Good: Prioritize by impact. Fix correctness first, then clarity, then style. **2. No positive feedback** Bad: Only listing problems. Good: Note what was done well. Reviewers who only criticize produce defensive engineers. **3. Vague feedback** Bad: "This function is too complex." Good: "This function does 3 things: validates input, transforms data, and saves to DB. Extract each into its own function so each can be read and tested independently." **4. Reviewing without running the code** Bad: Approving a PR without checking it builds and tests pass. Good: CI should enforce this automatically. If CI is absent, run tests locally before approving. ## Quality Checklist - [ ] Intent is clear - code reads without needing to decode it - [ ] Names reveal intent at every level (variables, functions, classes) - [ ] Functions have single responsibility and fit in one screen - [ ] Error handling is explicit - no silent failures - [ ] No unnecessary duplication - DRY applied - [ ] Tests cover happy path and failure cases - [ ] Must fix / should fix / consider clearly separated - [ ] At least one specific piece of positive feedback included
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · qa-aman/claude-skills | 90 | MIT |
| microsoft/aspire | 100 | MIT |
| kdlbs/kandev | 100 | AGPL-3.0 |
| dotnet/runtime | 100 | MIT |
| drosam/agents | 100 | MIT |
| ggml-org/llama.cpp | 100 | MIT |
| ShamelesAbyss/Nyx | 100 | Apache-2.0 |
| dzhng/jevgrep | 100 | MIT |
| iuliandita/skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version 7cc1fdb36651 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100review-pr
Review a pull request for code quality and security issues. Use when the user wants to review a PR, check PR code changes, or audit a pull request. Triggers on: "review PR", "review pull request", "check this PR", "the `review-pr` skill". - 100code-reviewing
Review code for quality, security, and best practices. Use when the user asks for code review, wants feedback on their code, mentions reviewing changes, or asks about code quality. - 82review-code
Use to review code. - 95pr-review
Review a PR for correctness, security, code quality, and testing issues. TRIGGER when user asks to review a PR, check PR quality, or give feedback on a PR. - 100code-review-lens
Use when the user says \"review this\", \"check my code\", or wants feedback on changes. Reviews for correctness, quality, security, and coding standards. - 100code-quality
Code review to find quality issues, style violations, and code smells. Triggers on: review, code review, quality, lint, code smell, analyze code.