multi-reviewer-patterns

Coordinate parallel code reviews across quality dimensions with deduplication and consolidated reporting.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill multi-reviewer-patterns-sanketadlak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-reviewer-patterns
Source: https://github.com/SanketAdlak/PDMProjectDesign/tree/main/.agents/skills/multi-reviewer-patterns
Command: npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill multi-reviewer-patterns-sanketadlak

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Running code reviews across multiple quality dimensions often produces overlapping findings, inconsistent severity ratings, and fragmented reports that are hard to act on. This Skill provides structured patterns for organizing multi-reviewer reviews, merging duplicate findings, calibrating severity, and producing a single consolidated report. ## Core Features & Use Cases - Review Dimension Allocation: Choose the right review dimensions (Security, Performance, Architecture, Testing, Accessibility) based on the type of change, with recommended combinations for common scenarios like API endpoints, frontend components, and database migrations. - Finding Deduplication: Apply deterministic merge rules for findings at the same file and line, handling conflicting severities and recommendations with reviewer attribution. - Severity Calibration: Use consistent criteria mapping impact and likelihood to Critical, High, Medium, and Low ratings, with domain-specific calibration rules. - Consolidated Reporting: Generate a standardized review report with findings grouped by severity and a per-dimension summary table. - Use Case: When reviewing a pull request that adds a new authenticated API endpoint, assign Security, Performance, and Architecture reviewers, merge their overlapping findings, calibrate severity, and output one prioritized report. ## Quick Start Organize a multi-dimension code review of my latest pull request covering security, performance, and architecture, then consolidate the findings into a single severity-ranked report.

Frequently Asked Questions about multi-reviewer-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize a code review across multiple reviewers?

Assign each reviewer a distinct quality dimension such as Security, Performance, Architecture, Testing, or Accessibility based on the type of change. The skill provides recommended dimension combinations for scenarios like API endpoints, frontend components, and database migrations.

How do I deduplicate findings from multiple code reviewers?

Merge findings that reference the same file and line and describe the same issue, crediting all reviewers. Keep different issues at the same location as separate co-located findings, and use the highest severity when merged findings conflict.

How do I calibrate severity ratings in code reviews?

Map each finding's impact and likelihood to Critical, High, Medium, or Low using the calibration criteria. For example, externally exploitable security vulnerabilities are always Critical or High, while style issues with no functional impact are Low.

Which review dimensions should I use for different types of changes?

Match dimensions to the change type: Security, Performance, and Architecture for API endpoints; Architecture, Testing, and Accessibility for frontend components; Performance and Architecture for database migrations; Security and Testing for authentication changes.

What checklists are included for each review dimension?

The references directory includes detailed checklists for Security (input handling, auth, secrets, dependencies), Performance (database, memory, computation), Architecture (design principles, structure, patterns), Testing (coverage, quality, maintainability), and Accessibility (structure, interaction, content).