multi-review

Orchestrate parallel peer reviews of code and delivery artifacts.

1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/cryptopafi/nexusos-skills --skill multi-review-cryptopafi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-review
Source: https://github.com/cryptopafi/nexusos-skills/tree/main/multi-review
Command: npx skills add https://github.com/cryptopafi/nexusos-skills --skill multi-review-cryptopafi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes uncertainty from post-build deliveries by running multiple specialized reviewers in parallel to detect security issues, correctness bugs, and integration regressions before merge decisions.

Core Features & Use Cases

  • Parallel specialized reviewers: Launches 3-5 reviewer agents (security, correctness, integration, plus optional style and performance) to evaluate a delivery concurrently.
  • Deterministic gating rules: Aggregates PASS/FAIL verdicts, enforces majority rules, blocks on any CRITICAL findings and on security HIGHs, and reports CONDITIONAL outcomes when applicable.
  • Robust fallbacks and persistence: Supports workspace and file targets, standalone file-only mode, timeout and skipped-review handling, and saves summaries to REVIEW.md and Cortex for trend analysis.
  • Integration points: Designed to be invoked manually or automatically as the IL-14 augmentation to verify-after-write pipelines after builder/fixer/integrator steps.

Quick Start

Run /multi-review on the most recent NexusOS delivery to produce a PASS, CONDITIONAL, or FAIL gate and a detailed findings report.

Frequently Asked Questions about multi-review

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

FAQPage Schema
How do I automate parallel peer review to gate code merges for security and correctness?

Automated parallel peer review gates merges by spawning 3-5 specialized reviewer agents to evaluate security, correctness, integration, style, and performance concurrently. It aggregates verdicts under strict majority rules, blocking merges on any CRITICAL or security HIGH findings.

What is the best way to run post-build verification on code deliveries before merging?

Post-build verification for code deliveries is best handled by orchestrating concurrent specialized reviewers that apply deterministic gating rules. This process evaluates integration regressions and correctness bugs, producing a PASS, CONDITIONAL, or FAIL gate alongside a detailed findings report.

Can I use automated code review to check individual files or do I need a full workspace directory?

Automated code review supports both standalone file-only mode and full workspace directory targets. You can apply the peer-review gate to individual files or entire NexusOS delivery directories for post-fix verification and CI pipeline gating.

Does the parallel peer-review gate block merges automatically on security findings?

Yes, the parallel peer-review gate blocks merges automatically on any CRITICAL findings and security HIGH findings. It enforces strict majority rules across all spawned reviewer agents and reports CONDITIONAL outcomes when applicable.

How does the code review process handle reviewer timeouts or skipped reviews?

The code review process handles reviewer timeouts and skipped reviews through robust fallback mechanisms. It applies a 120-second soft timeout for each specialized reviewer agent and persists the aggregated review summaries to REVIEW.md and Cortex for trend analysis.

Why should I use multiple specialized reviewers instead of a single automated code review?

Using multiple specialized reviewers removes uncertainty from post-build deliveries by concurrently evaluating security, correctness, integration, style, and performance. This parallel approach detects integration regressions and correctness bugs more effectively than a single review pass before merge decisions.