A code review catches bugs, security holes, and performance problems before they cause trouble. It looks at your changes from many angles. You get clear suggestions with code examples.
Give it a pull request URL, a diff, or a file path. It checks for SQL injection, missing edge cases, and slow queries. It also looks at naming and style.
If you connect your tools, it can pull diffs automatically and check against team standards.
Global
mkdir -p ~/.claude/skills/code-reviewProject
mkdir -p .claude/skills/code-reviewSource 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