explaingit

vikingmute/review-forge

17Audience · developerComplexity · 2/5Setup · easy

TLDR

A skill plugin for AI coding agents that runs multi-perspective code reviews, merges the findings into one checklist you approve, and then applies only the fixes you tick off before running your tests to verify them.

Mindmap

mindmap
  root((review-forge))
    What it does
      Multi-pass code review
      Synthesize findings
      Human approval step
      Verified fixes
    Workflow steps
      Review
      Synthesize
      Fix approved items
      Verify fixes
    Review targets
      Local changes
      Branch diffs
      Pull requests
      Commit ranges
    Supported agents
      Codex
      Cursor
      OpenCode
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Run a structured multi-pass code review on a pull request and get a single approved checklist before any code is changed.

USE CASE 2

Review local uncommitted changes with the AI, tick off only the issues you want fixed, and have the tool apply and verify those changes.

USE CASE 3

Merge review notes from different AI models into one ranked summary before deciding which fixes to approve.

Tech stack

Node.js

Getting it running

Difficulty · easy Time to first run · 30min

Installed via a short npx Skills CLI command, invoke it from Codex, Cursor, or OpenCode using $review-forge in your prompt.

In plain English

Review Forge is a skill plugin for AI coding agents that brings structure and accountability to the code review process. Instead of getting a single AI pass on your code and hoping it catches everything, Review Forge runs multiple review passes from different perspectives, then compiles the findings into one checklist you can inspect and approve before any changes are made. The core workflow has four steps. First, you run a review, which asks the AI to look at your local changes, a branch, a pull request, or a specific range of commits and produce a review file. Second, you synthesize, which merges multiple review files from different models or perspectives into a single summary. Third, you fix, which only touches the items you have checked off in that summary, then runs your tests. Fourth, you verify, which independently confirms that the fixes actually worked. That human approval step is a deliberate design choice. The checklist acts as a boundary: the tool will not implement a fix unless you have explicitly ticked the box. This keeps you in control even when the AI is doing most of the analysis work. All the files the workflow creates, including review notes, summaries, fix plans, and verification logs, land under a code_review/ folder inside your project. Each feature you review gets its own subfolder, so different code changes stay organized and traceable. If you do not want these files committed to version control, the README suggests adding code_review/ to your .gitignore. You install Review Forge using the Skills CLI tool with a short npx command, then invoke it from any compatible agent by referencing $review-forge in your prompt. It works with agents like Codex, Cursor, and OpenCode. Generated reports can follow your prompt language automatically, while internal status values stay in English for consistency across tools.

Copy-paste prompts

Prompt 1
Use review-forge to review my current branch diff against main. Show me the review checklist and explain the top three issues it found.
Prompt 2
I have a review-forge summary file and I've checked off five items. Now run the fix step and confirm the tests still pass afterward.
Prompt 3
Run review-forge on this pull request and synthesize findings from two different model passes into one ranked checklist.
Prompt 4
Set up review-forge in my project so review notes land in code_review/ and are excluded from git. Walk me through the install and first review run.
Open on GitHub → Explain another repo

← vikingmute on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.