This skill helps you review a pull request by reading the changes and writing structured feedback into a file. It focuses on bugs, security issues, and important code problems. Developers and teams can use it to get clear, machine-readable reviews without posting comments on GitHub.
The skill reads the diff and description from local files. It marks each comment with a label like CRITICAL, IMPORTANT, SUGGESTION, or NIT. This makes it easy to sort and act on feedback. The output goes into review.json for your workflow to publish.
It also supports special rules like checking against a spec document or a security companion skill. All findings stay in one file. This keeps your review process consistent and automated.
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