code-review-checklistlisted

A ten-category human code-review rubric — correctness, design, readability, testing, security, performance, documentation, dependencies, error handling, and style — plus process guidance on feedback tone, review size, and a pre-submit self-review pass. Use when a review verdict is actually being produced on a concrete change, such as reviewing a pull request or diff, self-reviewing before opening one, or defining a team's code review standards. Triggers include code review, review this PR, pull request review, review checklist, review standards. It is a rubric rather than an analyzer, so it does not apply to merely reading or explaining code, answering how something works, debugging, refactoring, or running linters, formatters, and type checkers.
pfangueiro/claude-code-agents · ★ 6 · Code & Development · score 76

Install: claude install-skill pfangueiro/claude-code-agents

# Code Review Checklist ## Overview This skill provides a systematic approach to code reviews, ensuring consistent quality standards across your codebase. Use it to conduct thorough, constructive code reviews that improve code quality and team knowledge sharing. ## When to Use This Skill - Reviewing pull requests - Defining or documenting a team's review standards - Establishing code review standards for your team - Self-reviewing code before submitting - Mentoring junior developers on code quality - Complementing the **code-quality agent** for comprehensive reviews ## Core Review Categories ### 1. Functionality & Correctness **Does the code work as intended?** - [ ] Code accomplishes the intended purpose - [ ] Edge cases are handled appropriately - [ ] Error handling is comprehensive - [ ] Input validation is present and correct - [ ] Boundary conditions are tested - [ ] No obvious bugs or logic errors - [ ] Code handles null/undefined/empty values safely **Questions to Ask:** - What happens if this API call fails? - Are all user inputs validated? - What if the array is empty? - Are there any race conditions? ### 2. Design & Architecture **Is the code well-designed?** - [ ] Code follows SOLID principles - [ ] Appropriate design patterns used - [ ] Separation of concerns is clear - [ ] No tight coupling between components - [ ] Abstractions are at the right level - [ ] Code is modular and reusable - [ ] No circular dependencies **Red Flags:** - God classes (doing