A code review checklist helps you check every part of a code change. You can catch bugs, security flaws, and performance problems before they reach users. Functionality, security, performance, and maintainability are all covered.
This guide walks you through each step of a review. You start by understanding the context and then move through functionality, code quality, security, performance, and tests. Each area has clear items to verify.
New developers can learn good review habits with this checklist. Teams can use it to make sure every pull request is checked the same way. Nothing gets missed when you follow the list.
Global
mkdir -p ~/.claude/skills/code-review-checklistProject
mkdir -p .claude/skills/code-review-checklistSource Repository
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Codebase Designmattpocock/skills
Create deep modules with tiny interfaces and lots of hidden logic for testability
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective