
multi-reviewer-patterns
Coordinate parallel code reviews across multiple quality dimensions
by wshobsonFree
Description
multi-reviewer-patterns is an agent skill from the wshobson/agents collection for coordinating several code reviews that run in parallel, each looking at a different quality dimension of the same change. Instead of one reviewer trying to check everything, the work is divided so that each reviewer covers one dimension, such as correctness, security or performance, and the results are then combined. The skill covers deciding which review dimensions to assign to which reviewer, deduplicating findings when two reviewers report the same problem, calibrating severity ratings so that a finding means the same thing whichever reviewer raised it, and producing a single consolidated report for the author. Calibration and deduplication are the parts that make parallel reviews useful rather than noisy. The skill applies when organizing a review that spans several dimensions, deciding which dimensions a change needs, merging findings from several reviewers, keeping severity labels consistent, and writing the consolidated review. It is meant for teams and agent setups that review large or risky changes and want thorough coverage without one long, unfocused review. The output still goes to a human author, who decides which findings to act on. The skill is installed with the skills CLI from the wshobson/agents repository. Its skills.sh page showed about 9.5K installs and passing results from three security audits at the time of the scan.…
Highlights
- Parallel reviews split by quality dimension
- Dimension allocation per reviewer
- Finding deduplication
- Severity calibration across reviewers
- Consolidated review report
- Installs with the skills CLI
Ratings & Reviews
No ratings yet
Be the first to rate multi-reviewer-patterns.
People also visit
multi-reviewer-patterns FAQ
What does this skill coordinate?
Several code reviews running in parallel, each focused on a different quality dimension of the same change.
Why deduplicate findings?
So two reviewers reporting the same problem produce one finding rather than two.
What does severity calibration mean here?
Making sure a severity rating means the same thing whichever reviewer gives it.
Who decides what to fix?
The consolidated report goes to the author, who decides which findings to act on.
How do I install it?
Run npx skills add https://github.com/wshobson/agents --skill multi-reviewer-patterns.
What security audits does it have?
skills.sh lists three audits: Gen Agent Trust Hub Pass, Socket Pass and Snyk Pass.
What are the best multi-reviewer-patterns alternatives?
Popular alternatives to multi-reviewer-patterns include ai-debt-detector, code-review-excellence and code-reviewer. See all multi-reviewer-patterns alternatives









