review-swarm

Automate independent reviews across Claude, Gemini, Codex, OpenCode, and Kimi.

14|6|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/fkguo/nullius --skill review-swarm-fkguo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-swarm
Source: https://github.com/fkguo/nullius/tree/main/skills/review-swarm
Command: npx skills add https://github.com/fkguo/nullius --skill review-swarm-fkguo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires opencode-cli-runner, claude-cli-runner, codex-cli-runner, gemini-cli-runner, kimi-cli-runner, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the process of obtaining independent, multi-backend reviews for various types of content, ensuring accuracy and reliability.

Core Features & Use Cases

  • Multi-backend Review: Conduct reviews across Claude, Gemini, Codex, OpenCode, and Kimi, ensuring diverse perspectives.
  • Review Contract Checking: Validate output format compliance and record results.
  • Fallback Policy: Apply fallback policy when a backend fails or returns invalid output.
  • Convergence Check: Gate on convergence (optional Jaccard similarity).
  • Use Case: Imagine you have a research paper that requires thorough, independent review. Use this Skill to run a review swarm with diverse reviewers, ensuring accuracy and consistency.

Quick Start

To start a multi-backend review swarm, run the following command:

python3 scripts/bin/run_multi_task.py \
  --out-dir /tmp/cross_family_review \
  --system /path/to/reviewer_system.md \
  --prompt /path/to/packet.md \
  --models codex/default,gemini/default,zhipuai-coding-plan/glm-5.2 \
  --check-review-contract

Frequently Asked Questions about review-swarm

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

FAQPage Schema
How do I automate independent code reviews across multiple AI backends?▼

You can automate independent code reviews across multiple AI backends like Claude, Gemini, Codex, OpenCode, and Kimi by running a review swarm script that dispatches prompts to each model and records their distinct outputs.

What is a review contract check for multi-backend review swarms?▼

A review contract check validates output format compliance during a multi-backend review swarm, ensuring that each AI backend returns results that meet predefined structural rules before recording them.

How do I run a cross-family review using Claude, Gemini, and Codex?▼

To run a cross-family review, execute the multi-task Python script with your system prompt, packet file, and a comma-separated list of target models, enabling the review contract flag to validate outputs.

Do I need specific runner skills installed to use a multi-backend review swarm?▼

Yes, you need backend-specific runner skills such as the claude-cli-runner, gemini-cli-runner, and codex-cli-runner available on your PATH to dispatch and execute the independent review tasks.

What happens when an AI backend fails during an automated review swarm?▼

When an AI backend fails or returns invalid output during an automated review swarm, the system applies a fallback policy to handle the failure gracefully and ensure the overall review process continues.

Can I check for output convergence when running multi-backend AI reviews?▼

Yes, you can gate the multi-backend review process on convergence by applying an optional Jaccard similarity check to measure the overlap and consistency of outputs from the different AI backends.