Multi-Reviewer Patterns

Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated…

You say
Buy it · $39 Read it before you buy $39 Written by wshobson · unverified publisher
Context cost
2.3k tokensestimated from the bundle, loaded when it triggers
Bundle
2 files · 9.3 kBtext throughout, nothing executable
Licence
MITpaid listing
Last change
v1.0.2
Servers it uses
Noneruns standalone

What it does

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.

Installed, it changes the agent in these ways.

What this skill changes about the agent is not written down here yet. The listing was collected from its source, and the description is in its own SKILL.md.

Expertise

Domain judgement the base model does not have.

collaboration

The skill itself

This is the whole product. A skill is instructions the model reads, so there is nothing behind the listing you cannot see first — the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md5.2 kB · 128 lines
--- name: multi-reviewer-patterns description: 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. version: 1.0.2 ---
7# Multi-Reviewer Patterns
8
9Patterns for coordinating parallel code reviews across multiple quality dimensions, deduplicating findings, calibrating severity, and producing consolidated reports.
10
11## When to Use This Skill
12
13- Organizing a multi-dimensional code review
14- Deciding which review dimensions to assign
15- Deduplicating findings from multiple reviewers
16- Calibrating severity ratings consistently
17- Producing a consolidated review report
18
19## Review Dimension Allocation
20
21### Available Dimensions
22
23| 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 |
30
31### Recommended Combinations
32
33| 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 |
40
41## Finding Deduplication
42
43When multiple reviewers report issues at the same location:
44
45### Merge Rules
46
471. **Same file:line, same issue** — Merge into one finding, credit all reviewers
482. **Same file:line, different issues** — Keep as separate findings
493. **Same issue, different locations** — Keep separate but cross-reference
504. **Conflicting severity** — Use the higher severity rating
515. **Conflicting recommendations** — Include both with reviewer attribution
52
53### Deduplication Process
54
55```
56For each finding in all reviewer reports:
57 1. Check if another finding references the same file:line
58 2. If yes, check if they describe the same issue
59 3. If same issue: merge, keeping the more detailed description
60 4. If different issue: keep both, tag as "co-located"
61 5. Use highest severity among merged findings
62```
63
64## Severity Calibration
65
66### Severity Criteria
67
68| 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 |
74
75### Calibration Rules
76
77- Security vulnerabilities exploitable by external users: always Critical or High
78- Performance issues in hot paths: at least Medium
79- Missing tests for critical paths: at least Medium
80- Accessibility violations for core functionality: at least Medium
81- Code style issues with no functional impact: Low
82
83## Consolidated Report Template
84
85```markdown
86## Code Review Report
87
88**Target**: {files/PR/directory}
89**Reviewers**: {dimension-1}, {dimension-2}, {dimension-3}
90**Date**: {date}
91**Files Reviewed**: {count}
92
93### Critical Findings ({count})
94
95#### [CR-001] {Title}
96
97**Location**: {file}:{line}
98**Dimension**: {Security/Performance/etc.}
99**Description**: {what was found}
100**Impact**: {what could happen}
101**Fix**: {recommended remediation}
102
103### High Findings ({count})
104
105...
106
107### Medium Findings ({count})
108
109...
110
111### Low Findings ({count})
112
113...
114
115### Summary
116
117| 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** |
123
124### Recommendation
125
126{Overall assessment and prioritized action items}
127```
128
In the file
SKILL.md659 words
Files2
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈80
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
2,245
on trigger
The instruction body and 1 supporting file, read only when the skill fires.
1.2%
of a 200k window
Ten skills this size would take about 12% of the window before you open a file.
050k100k150k200k context window

2.3k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Middling. Fine to keep on in a project where you use it weekly, worth unloading in one where you never do.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

Adoption
Installsnone yet
Ratingno reviews yet

The procedure it runs

The procedure has not been published here. It is in the skill’s own SKILL.md, which its author has not sent to the marketplace yet.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It writes no files and reaches no network. All it changes is how the model reasons and writes.

What it asks for
Writes filesno
Network accessno

Read from the allowed-tools line of this skill’s own SKILL.md. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

2 files, 9.3 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md5.2 kB
  • references/review-dimensions.md4.1 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 2 files you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

$39 once
Multi-Reviewer Patterns · MIT · wshobson
one-time
Price$39 once
LicenceMIT — the author’s, unchanged by this purchase
Paid throughStripe, once, on the card you add at the checkout
Keeps workingfor good — the files are yours once they are on disk
Updatesevery release of 1.x through this account

You can read the whole bundle before paying — the SKILL.md above is the product, not a preview of it. What the money buys is the delivery: the folder packaged and handed to your machine by key, every update its author ships, and our support if it does not do what this listing says. The terms of use are MIT, set by the author and unchanged by buying it here.

Payment runs through Stripe, on a page like this one rather than a redirect. Once there is an account it joins the same mcprush invoice as everything else you run, so there is never a second card to enter.

Which clients pick it up on their own

A skill is a folder of text. A client with a skills folder reads it without being told; everywhere else the same text works, it is just handed to the model rather than found.

Claude Code.claude/skills/
Claude Desktop
ChatGPT
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok.grok/skills/
Zed.agents/skills/
Windsurf.windsurf/skills/
Agent SDK.claude/skills/
HTTP / API
This release
Version1.0.2
Publishedno release date on file
Price$39
Referencewshobson/multi-reviewer-patterns

Versions

v1.0.2 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v1.0.2
  • No earlier releases have been published to the marketplace.
Pinning

Put wshobson/multi-reviewer-patterns@1.0.2 in the install command to hold this exact version. Without the suffix you get whatever is current the day you install, and nothing moves under you afterwards.

Reviews

no reviews yet · no installs yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Who can post

Only accounts that have had the skill installed for fourteen days, so a review is written after living with it rather than after reading it. Publishers may reply once.

Publisher
Servers0