SkillAgentSearch skills...

multi-reviewer-patterns

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.

Install / Use

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

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

93/100

Supported Platforms

Universal

Our assessment of multi-reviewer-patterns

multi-reviewer-patterns scores 93/100 on our quality scale, 570th of 4,698 Development & Engineering skills we index (top 13%).

Its SKILL.md is 5.1 KB long, well organised into 20 sections with 2 code examples: a solid amount of guidance for an agent.

With 39,920 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
18/20
Description
15/15
Adoption
20/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so multi-reviewer-patterns is actively maintained.
  • Our last check on 2026-10-25 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-25. Automated pattern scan on 2026-09-25. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

multi-reviewer-patterns compared with similar skills

All 4 of these similar skills score higher than multi-reviewer-patterns; compare them before choosing.

SkillScoreStarsUpdatedFormat
multi-reviewer-patterns (this skill)by wshobson9339.9k57d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install multi-reviewer-patterns?
Run npx skills add wshobson/agents --skill multi-reviewer-patterns. The install tabs above show the steps for each supported agent.
Which AI agents does multi-reviewer-patterns work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is multi-reviewer-patterns safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is multi-reviewer-patterns still maintained?
The repository was last updated about 2 months ago, so multi-reviewer-patterns is actively maintained.

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

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

  1. Same file:line, same issue — Merge into one finding, credit all reviewers
  2. Same file:line, different issues — Keep as separate findings
  3. Same issue, different locations — Keep separate but cross-reference
  4. Conflicting severity — Use the higher severity rating
  5. 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}

Related Skills

View on GitHub
GitHub Stars39.9k
CategoryDevelopment
Updated1mo ago
Forks4.3k

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions