A code reviewer looks at changes in your code and finds hidden problems. It spots bugs, security vulnerabilities like SQL injection, and messy code. The output is a clear report with prioritized feedback to fix issues.
You can use it when reviewing a pull request or checking code quality. It checks for naming issues, slow database queries, and design flaws. The report helps you know what to fix first.
Senior engineers rely on it to share knowledge and improve team code. It works with other tools for security and testing. The result is better code and fewer bugs in production.
Global
mkdir -p ~/.claude/skills/code-reviewerProject
mkdir -p .claude/skills/code-reviewerSource 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