Index of every page on this site: llms.txt
All skills
wshobson avatar

/multi-reviewer-patterns

@4220308
by Seth Hobsonwshobson/agents43k stars
4,518
Run it yourself

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.

  • 2 files
  • 9.1 KB
  • Updated 10 months ago
  • GitHub
Use this Skill: https://skilld.dev/gh/wshobson/agents/multi-reviewer-patterns

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈73 tokens for metadata: the name and description. ≈1.2k when used: this file. ≈1k more on demand in 1 file.

Description uses 3.7% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈294 characters, or 3.7%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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}

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No third-party reports yet.

Signed by skilld at 4220308. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 10 months ago
version
1.0.2
  • code-review
  • multi-reviewer
  • findings-deduplication
  • severity-calibration
  • quality-assurance
  • architecture-review
  • security-review
  • performance-review
  • reporting

README badge

README badge for wshobson/agents/multi-reviewer-patterns

Coordinates parallel code reviews across multiple quality dimensions (security, performance, architecture, testing, accessibility) with rules for deduplicating findings, calibrating severity consistently, and consolidating results into a single report. Use this skill when running multi-reviewer audits or need to merge overlapping findings with standardized severity ratings.

Generated from the current SKILL.md.

How do I decide which review dimensions to assign to different reviewers?
The skill provides a table of five dimensions (Security, Performance, Architecture, Testing, Accessibility) with guidance on when to include each. For example, always include Security for code handling user input, include Performance for data access changes, and include Accessibility for UI changes. Recommended combinations are provided for common scenarios like API endpoints, frontend components, and authentication changes.
What do I do when multiple reviewers report the same issue at the same location?
Merge the findings into one, crediting all reviewers. Use the higher severity rating if reviewers disagree, and keep the more detailed description. If reviewers report different issues at the same location, keep both as separate findings and tag them as co-located.
How should I calibrate severity ratings across different reviewers?
The skill provides explicit severity criteria (Critical, High, Medium, Low) based on impact and likelihood. Use the calibration rules provided: security vulnerabilities exploitable by external users are always Critical or High, performance issues in hot paths are at least Medium, and code style issues with no functional impact are Low.
What format should the consolidated review report follow?
The skill includes a template that organizes findings by severity level (Critical, High, Medium, Low), includes location and dimension for each finding, and concludes with a summary table showing finding counts by dimension and severity, plus an overall recommendation.

Generated from the current SKILL.md. These answers refresh after source changes.