review-forge

Coordinate auditable code review workflows across multiple LLMs or agents.

150|9|Updated May 29, 2026
One-click install
npx skills add https://github.com/vikingmute/review-forge --skill review-forge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-forge
Source: https://github.com/vikingmute/review-forge/tree/main
Command: npx skills add https://github.com/vikingmute/review-forge --skill review-forge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end, auditable code review workflows across multiple LLMs or agents, turning scattered feedback into a single coherent process.

Core Features & Use Cases

  • Synthesizes review perspectives into a unified checklist for fixes.
  • Isolates artifacts under code_review/ to keep product code clean and auditable.
  • Orchestrates review, synthesis, fix, verification, and status tracking across teams.

Quick Start

Invoke the skill to orchestrate a multi-model review workflow on the current feature branch.

Frequently Asked Questions about review-forge

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

FAQPage Schema
How do I coordinate code reviews across multiple LLMs for a feature branch?

Multi-agent code review works by applying multiple LLMs to your feature branches and commits, then synthesizing their scattered feedback into a single unified checklist to apply fixes and track status.

How do I synthesize scattered multi-agent feedback into a unified checklist for fixes?

You synthesize multi-agent feedback by orchestrating the review workflow across LLMs, which automatically consolidates their varied perspectives into a single coherent checklist for applying fixes and running tests.

Does this multi-model code review workflow isolate artifacts from my product code?

Yes, the multi-model code review workflow enforces strict artifact isolation under the code_review/ directory, keeping your product code clean while maintaining full traceability for audit purposes.

Can I run tests automatically after applying fixes from an automated code review?

Yes, you can run tests automatically after applying fixes, as the workflow orchestrates the sequence from review synthesis to fix application and final verification to track overall status.

What is the best way to track status and traceability for automated code reviews?

The best way to track status and traceability for automated code reviews is to orchestrate the process end-to-end, isolating artifacts in code_review/ while tracking synthesis, fixes, and verification across teams.

Do I need to provide optional scripts or references to use the multi-agent review workflow?

You do not need to provide optional scripts or references to use the workflow, as it supports optional inputs like scripts/, references/, and assets/ only as needed for specific review scenarios.