Multi-Reviewer Patterns
Patterns for coordinating parallel code reviews across multiple quality dimensions, deduplicating findings, calibrating severity, and producing consolidated reports.
When to Use This Skill
- Organizing a multi-dimensional code review
- Deciding which review dimensions to assign
- Deduplicating findings from multiple reviewers
- Calibrating severity ratings consistently
- Producing a consolidated review report
Review Dimension Allocation
Available Dimensions
| Dimension |
Focus |
When to Include |
| Security |
Vulnerabilities, auth, input validation |
Always for code handling user input or auth |
| Performance |
Query efficiency, memory, caching |
When changing data access or hot paths |
| Architecture |
SOLID, coupling, patterns |
For structural changes or new modules |
| Testing |
Coverage, quality, edge cases |
When adding new functionality |
| Accessibility |
WCAG, ARIA, keyboard nav |
For UI/frontend changes |
Recommended Combinations
| Scenario |
Dimensions |
| API endpoint changes |
Security, Performance, Architecture |
| Frontend component |
Architecture, Testing, Accessibility |
| Database migration |
Performance, Architecture |
| Authentication changes |
Security, Testing |
| Full feature review |
Security, Performance, Architecture, Testing |
Finding Deduplication
When multiple reviewers report issues at the same location:
Merge Rules
- Same file:line, same issue — Merge into one finding, credit all reviewers
- Same file:line, different issues — Keep as separate findings
- Same issue, different locations — Keep separate but cross-reference
- Conflicting severity — Use the higher severity rating
- Conflicting recommendations — Include both with reviewer attribution
Deduplication Process
For each finding in all reviewer reports:
1. Check if another finding references the same file:line
2. If yes, check if they describe the same issue
3. If same issue: merge, keeping the more detailed description
4. If different issue: keep both, tag as "co-located"
5. Use highest severity among merged findings
Severity Calibration
Severity Criteria
| Severity |
Impact |
Likelihood |
Examples |
| Critical |
Data loss, security breach, complete failure |
Certain or very likely |
SQL injection, auth bypass, data corruption |
| High |
Significant functionality impact, degradation |
Likely |
Memory leak, missing validation, broken flow |
| Medium |
Partial impact, workaround exists |
Possible |
N+1 query, missing edge case, unclear error |
| Low |
Minimal impact, cosmetic |
Unlikely |
Style issue, minor optimization, naming |
Calibration Rules
- Security vulnerabilities exploitable by external users: always Critical or High
- Performance issues in hot paths: at least Medium
- Missing tests for critical paths: at least Medium
- Accessibility violations for core functionality: at least Medium
- Code style issues with no functional impact: Low
Consolidated Report Template
## Code Review Report
**Target**: {files/PR/directory}
**Reviewers**: {dimension-1}, {dimension-2}, {dimension-3}
**Date**: {date}
**Files Reviewed**: {count}
### Critical Findings ({count})
#### [CR-001] {Title}
**Location**: `{file}:{line}`
**Dimension**: {Security/Performance/etc.}
**Description**: {what was found}
**Impact**: {what could happen}
**Fix**: {recommended remediation}
### High Findings ({count})
...
### Medium Findings ({count})
...
### Low Findings ({count})
...
### Summary
| Dimension | Critical | High | Medium | Low | Total |
| ------------ | -------- | ----- | ------ | ----- | ------ |
| Security | 1 | 2 | 3 | 0 | 6 |
| Performance | 0 | 1 | 4 | 2 | 7 |
| Architecture | 0 | 0 | 2 | 3 | 5 |
| **Total** | **1** | **3** | **9** | **5** | **18** |
### Recommendation
{Overall assessment and prioritized action items}
Source: wshobson/agents → plugins/agent-teams/skills/multi-reviewer-patterns/SKILL.md
1---2name: multi-reviewer-patterns3description: Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting. Use this skill when organizing multi-reviewer code reviews, calibrating finding severity, or consolidating review results.4---567# Multi-Reviewer Patterns89Patterns for coordinating parallel code reviews across multiple quality dimensions, deduplicating findings, calibrating severity, and producing consolidated reports.1011## When to Use This Skill1213- Organizing a multi-dimensional code review14- Deciding which review dimensions to assign15- Deduplicating findings from multiple reviewers16- Calibrating severity ratings consistently17- Producing a consolidated review report1819## Review Dimension Allocation2021### Available Dimensions2223| Dimension | Focus | When to Include |24| ----------------- | --------------------------------------- | ------------------------------------------- |25| **Security** | Vulnerabilities, auth, input validation | Always for code handling user input or auth |26| **Performance** | Query efficiency, memory, caching | When changing data access or hot paths |27| **Architecture** | SOLID, coupling, patterns | For structural changes or new modules |28| **Testing** | Coverage, quality, edge cases | When adding new functionality |29| **Accessibility** | WCAG, ARIA, keyboard nav | For UI/frontend changes |3031### Recommended Combinations3233| Scenario | Dimensions |34| ---------------------- | -------------------------------------------- |35| API endpoint changes | Security, Performance, Architecture |36| Frontend component | Architecture, Testing, Accessibility |37| Database migration | Performance, Architecture |38| Authentication changes | Security, Testing |39| Full feature review | Security, Performance, Architecture, Testing |4041## Finding Deduplication4243When multiple reviewers report issues at the same location:4445### Merge Rules46471. **Same file:line, same issue** — Merge into one finding, credit all reviewers482. **Same file:line, different issues** — Keep as separate findings493. **Same issue, different locations** — Keep separate but cross-reference504. **Conflicting severity** — Use the higher severity rating515. **Conflicting recommendations** — Include both with reviewer attribution5253### Deduplication Process5455```56For each finding in all reviewer reports:57 1. Check if another finding references the same file:line58 2. If yes, check if they describe the same issue59 3. If same issue: merge, keeping the more detailed description60 4. If different issue: keep both, tag as "co-located"61 5. Use highest severity among merged findings62```6364## Severity Calibration6566### Severity Criteria6768| Severity | Impact | Likelihood | Examples |69| ------------ | --------------------------------------------- | ---------------------- | -------------------------------------------- |70| **Critical** | Data loss, security breach, complete failure | Certain or very likely | SQL injection, auth bypass, data corruption |71| **High** | Significant functionality impact, degradation | Likely | Memory leak, missing validation, broken flow |72| **Medium** | Partial impact, workaround exists | Possible | N+1 query, missing edge case, unclear error |73| **Low** | Minimal impact, cosmetic | Unlikely | Style issue, minor optimization, naming |7475### Calibration Rules7677- Security vulnerabilities exploitable by external users: always Critical or High78- Performance issues in hot paths: at least Medium79- Missing tests for critical paths: at least Medium80- Accessibility violations for core functionality: at least Medium81- Code style issues with no functional impact: Low8283## Consolidated Report Template8485```markdown86## Code Review Report8788**Target**: {files/PR/directory}89**Reviewers**: {dimension-1}, {dimension-2}, {dimension-3}90**Date**: {date}91**Files Reviewed**: {count}9293### Critical Findings ({count})9495#### [CR-001] {Title}9697**Location**: `{file}:{line}`98**Dimension**: {Security/Performance/etc.}99**Description**: {what was found}100**Impact**: {what could happen}101**Fix**: {recommended remediation}102103### High Findings ({count})104105...106107### Medium Findings ({count})108109...110111### Low Findings ({count})112113...114115### Summary116117| Dimension | Critical | High | Medium | Low | Total |118| ------------ | -------- | ----- | ------ | ----- | ------ |119| Security | 1 | 2 | 3 | 0 | 6 |120| Performance | 0 | 1 | 4 | 2 | 7 |121| Architecture | 0 | 0 | 2 | 3 | 5 |122| **Total** | **1** | **3** | **9** | **5** | **18** |123124### Recommendation125126{Overall assessment and prioritized action items}127```128129---130131**Source:** [`wshobson/agents`](https://github.com/wshobson/agents) → `plugins/agent-teams/skills/multi-reviewer-patterns/SKILL.md`
wshobson