Sometimes code needs more than one set of eyes. This skill helps you organize parallel code reviews across different quality areas like security, performance, and testing. It shows how to assign the right reviewers, merge duplicate findings, and set consistent severity ratings.
The process keeps duplicate issues from cluttering the report. When two reviewers find the same problem, the system merges them. When they find different things, both stay. The final output is a consolidated report with clear priorities.
Anyone managing a team review or a multi-dimensional code check can use these patterns. The result is faster, clearer feedback without confusion or wasted effort.
Global
mkdir -p ~/.claude/skills/multi-reviewer-patternsProject
mkdir -p .claude/skills/multi-reviewer-patternsSource 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