A pull request review can catch bugs and improve code quality. This skill uses multiple smart agents to check every change in a structured way. It focuses on important issues like security and performance. The review only posts inline comments on the code itself. This keeps feedback clear and avoids extra noise. Developers get actionable advice without distraction. The skill even fills in a missing pull request description with a short summary.
You can tell the skill which areas to focus on. For example you can ask it to check security or performance. You can also set a minimum impact level for comments. Higher impact issues like critical or high come first. This helps teams prioritize what matters most. The skill works with Git to understand what files changed and how many lines were modified.
Managers and senior developers will find this useful for maintaining code standards. It automates the repetitive parts of code review. Team members can trust that every pull request gets a thorough, consistent check. The skill is built for modern development workflows and integrates smoothly with existing tools.
Global
mkdir -p ~/.claude/skills/review-prProject
mkdir -p .claude/skills/review-prSource 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