multi-reviewer-patterns

Name: multi-reviewer-patterns
Author: wshobson

38kstars4.1kforks

How to install multi-reviewer-patterns?

wshobson/agents/multi-reviewer-patterns

$npx -y skills add wshobson/agents --skill multi-reviewer-patterns

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# Multi-Reviewer Patterns
2
3	Patterns for coordinating parallel code reviews across multiple quality dimensions, deduplicating findings, calibrating severity, and producing consolidated reports.
4
5	## When to Use This Skill
6
7	- Organizing a multi-dimensional code review
8	- Deciding which review dimensions to assign
9	- Deduplicating findings from multiple reviewers
10	- Calibrating severity ratings consistently
11	- Producing a consolidated review report
12
13	## Review Dimension Allocation
14
15	### Available Dimensions
16
17	\| Dimension \| Focus \| When to Include \|
18	\| ----------------- \| --------------------------------------- \| ------------------------------------------- \|
19	\| Security \| Vulnerabilities, auth, input validation \| Always for code handling user input or auth \|
20	\| Performance \| Query efficiency, memory, caching \| When changing data access or hot paths \|
21	\| Architecture \| SOLID, coupling, patterns \| For structural changes or new modules \|
22	\| Testing \| Coverage, quality, edge cases \| When adding new functionality \|
23	\| Accessibility \| WCAG, ARIA, keyboard nav \| For UI/frontend changes \|
24
25	### Recommended Combinations
26
27	\| Scenario \| Dimensions \|
28	\| ---------------------- \| -------------------------------------------- \|
29	\| API endpoint changes \| Security, Performance, Architecture \|
30	\| Frontend component \| Architecture, Testing, Accessibility \|
31	\| Database migration \| Performance, Architecture \|
32	\| Authentication changes \| Security, Testing \|
33	\| Full feature review \| Security, Performance, Architecture, Testing \|
34
35	## Finding Deduplication
36
37	When multiple reviewers report issues at the same location:
38
39	### Merge Rules
40
41	1. Same file:line, same issue — Merge into one finding, credit all reviewers
42	2. Same file:line, different issues — Keep as separate findings
43	3. Same issue, different locations — Keep separate but cross-reference
44	4. Conflicting severity — Use the higher severity rating
45	5. Conflicting recommendations — Include both with reviewer attribution
46
47	### Deduplication Process
48
49	```
50	For each finding in all reviewer reports:
51	1. Check if another finding references the same file:line
52	2. If yes, check if they describe the same issue
53	3. If same issue: merge, keeping the more detailed description
54	4. If different issue: keep both, tag as "co-located"
55	5. Use highest severity among merged findings
56	```
57
58	## Severity Calibration
59
60	### Severity Criteria
61
62	\| Severity \| Impact \| Likelihood \| Examples \|
63	\| ------------ \| --------------------------------------------- \| ---------------------- \| -------------------------------------------- \|
64	\| Critical \| Data loss, security breach, complete failure \| Certain or very likely \| SQL injection, auth bypass, data corruption \|
65	\| High \| Significant functionality impact, degradation \| Likely \| Memory leak, missing validation, broken flow \|
66	\| Medium \| Partial impact, workaround exists \| Possible \| N+1 query, missing edge case, unclear error \|
67	\| Low \| Minimal impact, cosmetic \| Unlikely \| Style issue, minor optimization, naming \|
68
69	### Calibration Rules
70
71	- Security vulnerabilities exploitable by external users: always Critical or High
72	- Performance issues in hot paths: at least Medium
73	- Missing tests for critical paths: at least Medium
74	- Accessibility violations for core functionality: at least Medium
75	- Code style issues with no functional impact: Low
76
77	## Consolidated Report Template
78
79	```markdown
80	## Code Review Report
81
82	Target: {files/PR/directory}
83	Reviewers: {dimension-1}, {dimension-2}, {dimension-3}
84	Date: {date}
85	Files Reviewed: {count}
86
87	### Critical Findings ({count})
88
89	#### [CR-001] {Title}
90
91	Location: `{file}:{line}`
92	Dimension: {Security/Performance/etc.}
93	Description: {what was found}
94	Impact: {what could happen}
95	Fix: {recommended remediation}
96
97	### High Findings ({count})
98
99	...
100
101	### Medium Findings ({count})
102
103	...
104
105	### Low Findings ({count})
106
107	...
108
109	### Summary
110
111	\| Dimension \| Critical \| High \| Medium \| Low \| Total \|
112	\| ------------ \| -------- \| ----- \| ------ \| ----- \| ------ \|
113	\| Security \| 1 \| 2 \| 3 \| 0 \| 6 \|
114	\| Performance \| 0 \| 1 \| 4 \| 2 \| 7 \|
115	\| Architecture \|

People who liked this also viewed

6 picks

Type

multi-reviewer-patterns

38kstars4.1kforks

View on GitHub

How to install multi-reviewer-patterns?

wshobson/agents/multi-reviewer-patterns

$npx -y skills add wshobson/agents --skill multi-reviewer-patterns

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Multi-Reviewer Patterns
2
3	Patterns for coordinating parallel code reviews across multiple quality dimensions, deduplicating findings, calibrating severity, and producing consolidated reports.
4
5	## When to Use This Skill
6
7	- Organizing a multi-dimensional code review
8	- Deciding which review dimensions to assign
9	- Deduplicating findings from multiple reviewers
10	- Calibrating severity ratings consistently
11	- Producing a consolidated review report
12
13	## Review Dimension Allocation
14
15	### Available Dimensions
16
17	\| Dimension \| Focus \| When to Include \|
18	\| ----------------- \| --------------------------------------- \| ------------------------------------------- \|
19	\| Security \| Vulnerabilities, auth, input validation \| Always for code handling user input or auth \|
20	\| Performance \| Query efficiency, memory, caching \| When changing data access or hot paths \|
21	\| Architecture \| SOLID, coupling, patterns \| For structural changes or new modules \|
22	\| Testing \| Coverage, quality, edge cases \| When adding new functionality \|
23	\| Accessibility \| WCAG, ARIA, keyboard nav \| For UI/frontend changes \|
24
25	### Recommended Combinations
26
27	\| Scenario \| Dimensions \|
28	\| ---------------------- \| -------------------------------------------- \|
29	\| API endpoint changes \| Security, Performance, Architecture \|
30	\| Frontend component \| Architecture, Testing, Accessibility \|
31	\| Database migration \| Performance, Architecture \|
32	\| Authentication changes \| Security, Testing \|
33	\| Full feature review \| Security, Performance, Architecture, Testing \|
34
35	## Finding Deduplication
36
37	When multiple reviewers report issues at the same location:
38
39	### Merge Rules
40
41	1. Same file:line, same issue — Merge into one finding, credit all reviewers
42	2. Same file:line, different issues — Keep as separate findings
43	3. Same issue, different locations — Keep separate but cross-reference
44	4. Conflicting severity — Use the higher severity rating
45	5. Conflicting recommendations — Include both with reviewer attribution
46
47	### Deduplication Process
48
49	```
50	For each finding in all reviewer reports:
51	1. Check if another finding references the same file:line
52	2. If yes, check if they describe the same issue
53	3. If same issue: merge, keeping the more detailed description
54	4. If different issue: keep both, tag as "co-located"
55	5. Use highest severity among merged findings
56	```
57
58	## Severity Calibration
59
60	### Severity Criteria
61
62	\| Severity \| Impact \| Likelihood \| Examples \|
63	\| ------------ \| --------------------------------------------- \| ---------------------- \| -------------------------------------------- \|
64	\| Critical \| Data loss, security breach, complete failure \| Certain or very likely \| SQL injection, auth bypass, data corruption \|
65	\| High \| Significant functionality impact, degradation \| Likely \| Memory leak, missing validation, broken flow \|
66	\| Medium \| Partial impact, workaround exists \| Possible \| N+1 query, missing edge case, unclear error \|
67	\| Low \| Minimal impact, cosmetic \| Unlikely \| Style issue, minor optimization, naming \|
68
69	### Calibration Rules
70
71	- Security vulnerabilities exploitable by external users: always Critical or High
72	- Performance issues in hot paths: at least Medium
73	- Missing tests for critical paths: at least Medium
74	- Accessibility violations for core functionality: at least Medium
75	- Code style issues with no functional impact: Low
76
77	## Consolidated Report Template
78
79	```markdown
80	## Code Review Report
81
82	Target: {files/PR/directory}
83	Reviewers: {dimension-1}, {dimension-2}, {dimension-3}
84	Date: {date}
85	Files Reviewed: {count}
86
87	### Critical Findings ({count})
88
89	#### [CR-001] {Title}
90
91	Location: `{file}:{line}`
92	Dimension: {Security/Performance/etc.}
93	Description: {what was found}
94	Impact: {what could happen}
95	Fix: {recommended remediation}
96
97	### High Findings ({count})
98
99	...
100
101	### Medium Findings ({count})
102
103	...
104
105	### Low Findings ({count})
106
107	...
108
109	### Summary
110
111	\| Dimension \| Critical \| High \| Medium \| Low \| Total \|
112	\| ------------ \| -------- \| ----- \| ------ \| ----- \| ------ \|
113	\| Security \| 1 \| 2 \| 3 \| 0 \| 6 \|
114	\| Performance \| 0 \| 1 \| 4 \| 2 \| 7 \|
115	\| Architecture \|

People who liked this also viewed

6 picks

Type