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}
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---56# Multi-Reviewer Patterns78Patterns for coordinating parallel code reviews across multiple quality dimensions, deduplicating findings, calibrating severity, and producing consolidated reports.910## When to Use This Skill1112- Organizing a multi-dimensional code review13- Deciding which review dimensions to assign14- Deduplicating findings from multiple reviewers15- Calibrating severity ratings consistently16- Producing a consolidated review report1718## Review Dimension Allocation1920### Available Dimensions2122| Dimension | Focus | When to Include |23| ----------------- | --------------------------------------- | ------------------------------------------- |24| **Security** | Vulnerabilities, auth, input validation | Always for code handling user input or auth |25| **Performance** | Query efficiency, memory, caching | When changing data access or hot paths |26| **Architecture** | SOLID, coupling, patterns | For structural changes or new modules |27| **Testing** | Coverage, quality, edge cases | When adding new functionality |28| **Accessibility** | WCAG, ARIA, keyboard nav | For UI/frontend changes |2930### Recommended Combinations3132| Scenario | Dimensions |33| ---------------------- | -------------------------------------------- |34| API endpoint changes | Security, Performance, Architecture |35| Frontend component | Architecture, Testing, Accessibility |36| Database migration | Performance, Architecture |37| Authentication changes | Security, Testing |38| Full feature review | Security, Performance, Architecture, Testing |3940## Finding Deduplication4142When multiple reviewers report issues at the same location:4344### Merge Rules45461. **Same file:line, same issue** — Merge into one finding, credit all reviewers472. **Same file:line, different issues** — Keep as separate findings483. **Same issue, different locations** — Keep separate but cross-reference494. **Conflicting severity** — Use the higher severity rating505. **Conflicting recommendations** — Include both with reviewer attribution5152### Deduplication Process5354```55For each finding in all reviewer reports:56 1. Check if another finding references the same file:line57 2. If yes, check if they describe the same issue58 3. If same issue: merge, keeping the more detailed description59 4. If different issue: keep both, tag as "co-located"60 5. Use highest severity among merged findings61```6263## Severity Calibration6465### Severity Criteria6667| Severity | Impact | Likelihood | Examples |68| ------------ | --------------------------------------------- | ---------------------- | -------------------------------------------- |69| **Critical** | Data loss, security breach, complete failure | Certain or very likely | SQL injection, auth bypass, data corruption |70| **High** | Significant functionality impact, degradation | Likely | Memory leak, missing validation, broken flow |71| **Medium** | Partial impact, workaround exists | Possible | N+1 query, missing edge case, unclear error |72| **Low** | Minimal impact, cosmetic | Unlikely | Style issue, minor optimization, naming |7374### Calibration Rules7576- Security vulnerabilities exploitable by external users: always Critical or High77- Performance issues in hot paths: at least Medium78- Missing tests for critical paths: at least Medium79- Accessibility violations for core functionality: at least Medium80- Code style issues with no functional impact: Low8182## Consolidated Report Template8384```markdown85## Code Review Report8687**Target**: {files/PR/directory}88**Reviewers**: {dimension-1}, {dimension-2}, {dimension-3}89**Date**: {date}90**Files Reviewed**: {count}9192### Critical Findings ({count})9394#### [CR-001] {Title}9596**Location**: `{file}:{line}`97**Dimension**: {Security/Performance/etc.}98**Description**: {what was found}99**Impact**: {what could happen}100**Fix**: {recommended remediation}101102### High Findings ({count})103104...105106### Medium Findings ({count})107108...109110### Low Findings ({count})111112...113114### Summary115116| Dimension | Critical | High | Medium | Low | Total |117| ------------ | -------- | ----- | ------ | ----- | ------ |118| Security | 1 | 2 | 3 | 0 | 6 |119| Performance | 0 | 1 | 4 | 2 | 7 |120| Architecture | 0 | 0 | 2 | 3 | 5 |121| **Total** | **1** | **3** | **9** | **5** | **18** |122123### Recommendation124125{Overall assessment and prioritized action items}126```
wesleyegberto