Reviewing code before it gets merged is a key step in building reliable software. This skill guides you through a complete code review process that covers code quality, security checks, performance, and maintainability. It helps you give constructive feedback that is respectful and clear.
Whether you are reviewing a pull request or mentoring a teammate, the process starts with an initial assessment. Then you dive into code quality, security, performance, and testing reviews. Each section offers specific best practices to follow and common pitfalls to avoid.
By using this skill you can catch bugs early, improve code standards, and help your team grow. It turns code review into a structured and positive experience for everyone involved.
Global
mkdir -p ~/.claude/skills/code-review-analysisProject
mkdir -p .claude/skills/code-review-analysisSource Repository
Web Design Guidelinesvercel-labs/agent-skills
Review your UI code for compliance with web interface guidelines
Improve Codebase Architecturemattpocock/skills
Scan your codebase for architecture improvements with visual reports and pick one to refactor
Zoom Outmattpocock/skills
Get a big picture view of your code with a simple map of modules and callers
Caveman Reviewjuliusbrussee/caveman
Ultra-compressed one-line code review comments that cut noise
Requesting Code Reviewobra/superpowers
Catch code issues early with focused automated reviews before every merge
Receiving Code Reviewobra/superpowers
Think first, then code. Verify feedback before making changes. Stay objective
Auditpbakaus/impeccable
Audit your code for accessibility performance theming and anti-patterns
Request Refactor Planmattpocock/skills
Plan safe code refactors with tiny commits and clear GitHub issues