code-review

Orchestrate multi-agent code review workflows to generate structured review documents from patch diffs.

581|102|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/juicesharp/rpiv-mono --skill code-review-juicesharp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/juicesharp/rpiv-mono/tree/main/packages/rpiv-pi/skills/code-review
Command: npx skills add https://github.com/juicesharp/rpiv-mono --skill code-review-juicesharp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates multi-agent code review workflows to generate structured review artifacts from diffs and patches, reducing manual review time.

Core Features & Use Cases

  • Wave-based review: coordinates dedicated wave-1/2/3 agents to assess quality, security, dependencies, and gating predicates across changed files.
  • Artifact generation: outputs a comprehensive review document and a discovery map for downstream tooling.
  • Use Case: when a team submits a patch or branch, the Skill produces a full review report describing findings and recommended actions.

Quick Start

Provide a patch or branch to the review workflow to generate a structured review document.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I automate code review for feature branches and patches?

Automate code review by orchestrating multiple AI agents to analyze patch diffs and commits, evaluating quality, security, and dependencies to produce a structured review document.

Can I review changes across a monorepo using AI-assisted diff analysis?

Yes, AI-assisted diff analysis evaluates changed files across monorepos by coordinating wave-based agents to assess gating predicates and governance signals, outputting a discovery map.

How does multi-agent code review work for security and dependency checks?

Multi-agent code review works by deploying dedicated wave-1/2/3 agents to evaluate security, dependencies, and governance signals across changed files, generating a comprehensive review artifact.

What is the best way to generate a structured review document from a git patch?

The best way to generate a structured review document from a git patch is providing the diff to an orchestrated review workflow that outputs findings and recommended actions.

Do I need a specific patch diff format to run automated code reviews?

Yes, automated code reviews require access to patch diffs formatted as .git/code-review-patch.diff to analyze changes and output a standardized review document for downstream tooling.

What are the limitations of using AI-assisted workflows for code review?

AI-assisted code review workflows are limited by their dependency on provided patch diffs and cannot evaluate code outside the submitted changes or patches without direct file access.