fusion-review

Runs parallel code reviews across multiple LLMs and merges findings into one report.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/Cohey0727/CodingAgentTools --skill fusion-review-cohey0727
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fusion-review
Source: https://github.com/Cohey0727/CodingAgentTools/tree/main/skills/fusion-review
Command: npx skills add https://github.com/Cohey0727/CodingAgentTools --skill fusion-review-cohey0727

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Single-model code reviews carry one model's biases and blind spots. This Skill sends the same review request to several LLMs in parallel, then has the host model verify each finding against the actual code and merge the survivors into one consolidated review. ## Core Features & Use Cases - Parallel multi-LLM review: Dispatches the same prompt to every enabled reviewer in llms.json (including the current Claude session itself) via background processes, with per-model timeouts. - Full-repository context: Checks out the review target into a disposable git worktree so reviewers can compare against existing conventions, search for duplicated utilities, and verify DRY violations instead of judging the diff in isolation. - Guideline-aware prompting: Collects CLAUDE.md, lint configs, and style guides into the prompt so reviewers judge against written project rules. - Meta-review fusion: The host model reviews the reviewers' findings one by one, discarding false positives and duplicates, then writes a single verdict with severity-ranked findings. - Two output modes: Local mode writes review.md to a temp directory; PR mode posts inline comments and a summary to a GitHub pull request via gh api. - Use Case: Before merging a large feature branch, ask for a multi-model review of the local diff; receive one deduplicated, fact-checked findings list instead of four raw model opinions. ## Quick Start Ask the assistant to run a fusion review of the uncommitted local changes and report the consolidated findings.

Frequently Asked Questions about fusion-review

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

FAQPage Schema
How do I get multiple LLMs to review the same code change?▼

Configure each reviewer as an entry in llms.json with a name, schema, and command, then invoke the skill on a diff or PR. It launches all enabled reviewers in parallel, collects their outputs, and merges verified findings into one report.

How do I add another model to the multi-LLM review?▼

Add one entry to llms.json with schema "stdin" and a command like "opencode run --model <provider>/<id> --agent plan". Check available models with "opencode models"; edit the repo-side file since the runtime path is a symlink.

Can this review a GitHub pull request with inline comments?▼

Yes. Passing a PR number or URL switches to PR mode: it fetches the PR head into a worktree, runs the parallel reviews, and posts one review with inline comments via "gh api" using event COMMENT, leaving approve/reject decisions to humans.

Why does the review use a git worktree instead of just the diff?▼

A diff alone cannot reveal whether code follows existing conventions or reimplements existing utilities. The worktree gives every reviewer read-only access to the full repository so they can compare patterns and search for duplicated logic.

What happens when one of the review models times out or fails?▼

Failed, timed-out, or empty responses are skipped without retry; the fusion step proceeds with the remaining outputs. If all reviewers fail, the skill reports the error logs instead of producing a review.

What are the limitations of multi-model code review?▼

Each invocation incurs API costs from every enabled provider, so it suits changes that genuinely need multiple perspectives. External reviewers run read-only via the plan agent, and majority agreement is not trusted blindly since all models can share the same misunderstanding.