Code Review Skill
awesome-skills/code-review-skill
Provides comprehensive code review guidance for React 19, Vue 3, Angular 17+, Svelte 5, Rust, TypeScript, Java, Java 8, PHP, Ruby, Rails, Python, Django, FastAPI, Go, C/.NET, Kotlin, Swift, Dart…
Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting.
Install Multi Reviewer Patterns
$ npx skills add wshobson/agents --skill multi-reviewer-patterns -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install wshobson/agents multi-reviewer-patterns --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/agent-teams/skills/multi-reviewer-patterns .claude/skills/multi-reviewer-patterns && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "multi-reviewer-patterns" agent skill from https://github.com/wshobson/agents/tree/main/plugins/agent-teams/skills/multi-reviewer-patterns into .claude/skills/multi-reviewer-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "multi-reviewer-patterns", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/wshobson/agents/tree/main/plugins/agent-teams/skills/multi-reviewer-patternsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add wshobson/agents --skill multi-reviewer-patterns -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install wshobson/agents multi-reviewer-patterns --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/agent-teams/skills/multi-reviewer-patterns .agents/skills/multi-reviewer-patterns && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "multi-reviewer-patterns" agent skill from https://github.com/wshobson/agents/tree/main/plugins/agent-teams/skills/multi-reviewer-patterns into .agents/skills/multi-reviewer-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "multi-reviewer-patterns", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wshobson/agents --skill multi-reviewer-patterns -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install wshobson/agents multi-reviewer-patterns --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/agent-teams/skills/multi-reviewer-patterns .cursor/skills/multi-reviewer-patterns && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "multi-reviewer-patterns" agent skill from https://github.com/wshobson/agents/tree/main/plugins/agent-teams/skills/multi-reviewer-patterns into .cursor/skills/multi-reviewer-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "multi-reviewer-patterns", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/wshobson/agents.git --path plugins/agent-teams/skills/multi-reviewer-patterns--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add wshobson/agents --skill multi-reviewer-patterns -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install wshobson/agents multi-reviewer-patterns --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/agent-teams/skills/multi-reviewer-patterns .gemini/skills/multi-reviewer-patterns && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "multi-reviewer-patterns" agent skill from https://github.com/wshobson/agents/tree/main/plugins/agent-teams/skills/multi-reviewer-patterns into .gemini/skills/multi-reviewer-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "multi-reviewer-patterns", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install wshobson/agents multi-reviewer-patternsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add wshobson/agents --skill multi-reviewer-patterns -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/agent-teams/skills/multi-reviewer-patterns .github/skills/multi-reviewer-patterns && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "multi-reviewer-patterns" agent skill from https://github.com/wshobson/agents/tree/main/plugins/agent-teams/skills/multi-reviewer-patterns into .github/skills/multi-reviewer-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "multi-reviewer-patterns", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wshobson/agents --skill multi-reviewer-patterns -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install wshobson/agents multi-reviewer-patterns --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wshobson/agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/agent-teams/skills/multi-reviewer-patterns .opencode/skills/multi-reviewer-patterns && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "multi-reviewer-patterns" agent skill from https://github.com/wshobson/agents/tree/main/plugins/agent-teams/skills/multi-reviewer-patterns into .opencode/skills/multi-reviewer-patterns/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "multi-reviewer-patterns", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
multi-reviewer-patterns- GitHub stars
- 40k
- Token cost
- ~1.3k tokens
- SKILL.md length
- 310 words
- Files
- 2 (incl. references)
- Skills in repo
- 142
- Repo updated
- First seen
- Licence
- MIT
At a glance
Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting.
- Works in 5 steps: Same file:line, same issue — Merge into… → Same file:line, different issues — Keep… → Same issue, different locations — Keep… → …
- Organizing multi-reviewer code reviews
- SKILL.md covers When to Use This Skill, Review Dimension Allocation, Finding Deduplication and Severity Calibration, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Multi Reviewer Patterns is an agent skill from wshobson/agents. 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.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/review-dimensions.md`).
It sits in Development, covering Code review, Data cleaning and Performance reviews. The repository describes itself as: Multi-harness agentic plugin marketplace for Claude Code, Codex, Cursor, OpenCode, GitHub Copilot, Google Antigravity, and Pi. The licence is MIT.
When your agent uses it
- Organizing multi-reviewer code reviews
- Calibrating finding severity
- Consolidating review results
Example prompts
- “/multi-reviewer-patterns”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Same file:line, same issue — Merge into one finding, credit all reviewers
- Same file:line, different issues — Keep as separate findings
- Same issue, different locations — Keep separate but cross-reference
- Conflicting severity — Use the higher severity rating
- Conflicting recommendations — Include both with reviewer attribution
What it can do on your machine
Read from SKILL.md and the folder at commit 46891e7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Multi Reviewer Patterns loads about 1.3k tokens when it runs, and up to ~2.3k if it reads all its reference files. Until then it costs about 73 tokens; SKILL.md has 310 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from wshobson/agents at commit 46891e7, republished under its MIT licence (© wshobson). 310 words, ~1,296 tokens.
Download SKILL.mdSave it as
.claude/skills/multi-reviewer-patterns/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- 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
- Same file:line, same issue — Merge into one finding, credit all reviewers
- Same file:line, different issues — Keep as separate findings
- Same issue, different locations — Keep separate but cross-reference
- Conflicting severity — Use the higher severity rating
- 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 findingsSeverity 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}© wshobson, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in plugins/agent-teams/skills/multi-reviewer-patterns of wshobson/agents.
- SKILL.md
- references/review-dimensions.md
Open the folder on GitHubat commit 46891e7
Compare with similar skills
Multi Reviewer Patterns next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Multi Reviewer Patterns this skillwshobson/agents | 40k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Code Review Skillawesome-skills/code-review-skill | 2.1k | — | ~2.8k | Automated safety check: Notes | MIT | |
| Scholar Code Reviewjoshzyj/open-scholar-skill | 168 | — | ~8.8k | Automated safety check: Pass | Custom licence | |
| Wp Performance Reviewelvismdev/claude-wordpress-skills | 235 | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Scholar Code Review
joshzyj/open-scholar-skill
Systematic multi-agent code review of all analysis scripts produced in a project.
Wp Performance Review
elvismdev/claude-wordpress-skills
WordPress performance code review and optimization analysis.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Code Review Checklist
shareAI-lab/learn-claude-code
Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.
Backend Code Review
langflow-ai/langflow
Review backend code for quality, security, maintainability, and best practices based on established checklist rules.
More from wshobson/agents
All 142 skills in this repoBilling Automation
wshobson/agents
Covers building subscription billing: billing cycles, subscription states, invoice generation, proration, tax handling and dunning for failed payments.
Cloud Cost Optimization
wshobson/agents
Cuts cloud spend across AWS, Azure, GCP and OCI with cost tagging, rightsizing, commitment and spot pricing models, and architecture changes.
Python Performance Optimization
wshobson/agents
Profiles slow Python code with cProfile and memory profilers, then applies targeted fixes for CPU, memory, I/O and query bottlenecks.
Portfolio Risk Metrics
wshobson/agents
Covers portfolio risk measurement with VaR, CVaR, Sharpe, Sortino and drawdown, plus guidance on limits, stress tests and tail risk.
Bats Shell Testing Patterns
wshobson/agents
Writes unit tests for shell scripts with Bats: error-condition tests, fixtures and mocks, cross-shell checks, parallel runs, helper files and CI integration.
DGX Spark Memory and Thermal Ops
wshobson/agents
Plans memory headroom, works through out-of-memory failures and watches temperature and power during long ML training jobs on NVIDIA DGX Spark.
Related
Categories
Questions about Multi Reviewer Patterns
What does Multi Reviewer Patterns do?
Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting. Multi Reviewer Patterns is an agent skill from wshobson/agents. Coordinate parallel code reviews across multiple quality dimensions with finding deduplication, severity calibration, and consolidated reporting.
When should I use Multi Reviewer Patterns?
Multi Reviewer Patterns fits situations like: organizing multi-reviewer code reviews; calibrating finding severity; consolidating review results.
How do I install Multi Reviewer Patterns in Claude Code?
Run `npx skills add wshobson/agents --skill multi-reviewer-patterns -a claude-code`. Or copy the skill folder (plugins/agent-teams/skills/multi-reviewer-patterns in wshobson/agents) into .claude/skills/multi-reviewer-patterns in your project. Claude Code loads it when a task matches its description.
How do I install Multi Reviewer Patterns in Codex?
Run `npx skills add wshobson/agents --skill multi-reviewer-patterns -a codex`. Or copy the skill folder (plugins/agent-teams/skills/multi-reviewer-patterns in wshobson/agents) into .agents/skills/multi-reviewer-patterns in your project. Codex loads it when a task matches its description.
Can I use Multi Reviewer Patterns in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wshobson/agents --skill multi-reviewer-patterns -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/multi-reviewer-patterns, .gemini/skills/multi-reviewer-patterns, .github/skills/multi-reviewer-patterns and .opencode/skills/multi-reviewer-patterns in your project.
What does Multi Reviewer Patterns need to run?
SKILL.md names no scripts, command-line tools or credentials: Multi Reviewer Patterns is instructions for the agent only.
Does Multi Reviewer Patterns access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Multi Reviewer Patterns safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Multi Reviewer Patterns use?
Multi Reviewer Patterns is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Multi Reviewer Patterns use?
About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1k tokens, read only when the agent opens those files.
What are the alternatives to Multi Reviewer Patterns?
Skills that share tags, products or a category with Multi Reviewer Patterns: Code Review Skill (awesome-skills/code-review-skill, 2.1k stars), Scholar Code Review (joshzyj/open-scholar-skill, 168 stars), Wp Performance Review (elvismdev/claude-wordpress-skills, 235 stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Multi Reviewer Patterns?
wshobson (a GitHub user) maintains it in wshobson/agents, which has 40,287 GitHub stars. The repository holds 142 skills in this directory. The repository was last updated on October 5, 2026.
Source: wshobson/agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.