parallel-code-review

Launch three parallel code reviewers and aggregate findings into a BLOCK/FIX/APPROVE verdict.

415|44|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/notque/claude-code-toolkit --skill parallel-code-review-notque
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallel-code-review
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/parallel-code-review
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill parallel-code-review-notque

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Parallel code review orchestration accelerates PR feedback by running three specialized reviewers at once and unifying their findings.

Core Features & Use Cases

  • Parallel reviewer dispatch: security, business logic, and architecture reviews run in parallel.
  • Severity-aware aggregation: merge findings into BLOCK/FIX/APPROVE verdict.
  • Read-only review: reviewers do not modify code and include file:line references.

Quick Start

Trigger the parallel-code-review workflow on a PR to launch three reviewers in parallel and produce a unified BLOCK/FIX/APPROVE verdict.

Frequently Asked Questions about parallel-code-review

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

FAQPage Schema
How do I automate parallel code reviews for large pull requests?

Automate parallel code reviews by dispatching three specialized reviewers simultaneously to cover security, business logic, and architecture. This orchestration accelerates PR feedback by unifying findings from multiple concurrent analyses into a single aggregated result.

What is severity-based aggregation in PR analysis?

Severity-based aggregation in PR analysis merges findings from multiple parallel reviewers into a unified verdict. It evaluates the severity of each detected issue to produce a final BLOCK, FIX, or APPROVE decision for the pull request.

When do I need to run parallel code reviews instead of a single review?

Run parallel code reviews when handling pull requests with 5+ files or complex, security-sensitive changes. This approach ensures comprehensive coverage across security, business logic, and architecture domains simultaneously.

Does parallel code review modify my source code during analysis?

Parallel code review operates strictly as a read-only analysis and does not modify your source code. Reviewers only analyze the changes and provide feedback with specific file and line references for you to act upon.

How do I trigger a parallel code review workflow?

Trigger the parallel code review workflow by applying it to a target pull request. This action launches three reviewers in parallel to analyze the changes and produce a unified BLOCK, FIX, or APPROVE verdict.

What are the limitations of using automated parallel PR analysis?

Automated parallel PR analysis is limited to read-only feedback and requires an optional re-run to verify critical fixes. It is specifically designed for large or security-sensitive PRs and may be excessive for simple, small-scale changes.