Code Review And Quality
addyosmani/agent-skillsEvery code change gets checked before it joins the main branch. This review looks at five important areas: correctness, readability, architecture, security, and performance. The goal is to make the codebase better over time, not to demand perfection.
You should approve a change if it clearly improves overall code health. Even if it is not perfect, that is fine. Do not block a change just because you would have written it differently. Focus on whether the change follows project rules and makes the code stronger.
Use this review before merging any pull request or after finishing a feature. It works for code written by you, another person, or an AI agent. The review checks for errors, confusing names, broken patterns, security holes, and slow performance.
Add Code Review And Quality skill to your workflow
Global
mkdir -p ~/.claude/skills/code-review-and-qualityProject
mkdir -p .claude/skills/code-review-and-qualitySource Repository
More Code Review & Quality Claude Code Skills
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