auto-review-loop

Automates multi-round research review cycles with independent cross-model reviewers until a passing verdict.

Updated Aug 18, 2026
One-click install
npx skills add https://github.com/Nitrogen216/awesome-dsh-mods --skill auto-review-loop-nitrogen216
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-review-loop
Source: https://github.com/Nitrogen216/awesome-dsh-mods/tree/main/modes/dsh-autoresearch/vendor/aris-upstream/skills/auto-review-loop
Command: npx skills add https://github.com/Nitrogen216/awesome-dsh-mods --skill auto-review-loop-nitrogen216

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research work needs rigorous, adversarial review before submission, but manual peer review is slow and self-review is biased. This Skill runs an autonomous review-fix-re-review loop with an independent reviewer model until the work earns a policy-approved positive assessment or the round limit is reached. ## Core Features & Use Cases - Autonomous Review Loop: Iterates review, fix implementation, and re-review for up to 4 rounds, stopping only when score >= 6/10 and verdict is "ready" or "almost". - Multi-Backend Reviewer Routing: Selects reviewers across Copilot native rubber-duck subagents, Codex MCP, or manual review, enforcing opposite model families for independent assessment. - State Persistence & Recovery: Writes REVIEW_STATE.json and an append-only ACQUITTAL_LOG.jsonl so loops survive context compaction and remain auditable per run_id. - Adjustable Difficulty: Medium, hard (reviewer memory + debate), and nightmare (direct repo access + adversarial verification) modes control how adversarial the reviewer is. - Use Case: After finishing experiments for a paper draft, run the loop so an independent GPT-family reviewer attacks your Claude-written claims, you implement the minimum fixes, and the cycle repeats until the work is judged submission-ready. ## Quick Start Ask the agent to run the auto review loop on your current research draft, for example: "Run auto-review-loop on the paper draft and experiment results in this project."

Frequently Asked Questions about auto-review-loop

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

FAQPage Schema
How do I run an autonomous review loop on a research paper draft?▼

Invoke the skill with a topic or scope argument, and it reviews your claims, code, and raw results through an independent reviewer, implements the minimum fixes, and re-reviews. The loop stops when the score reaches 6/10 with a ready or almost verdict, or after 4 rounds.

What reviewer backends does the auto review loop support?▼

It supports a Copilot native rubber-duck subagent, a compatibility copilot --agent subprocess, Codex via MCP tools, and a manual review MCP backend. With no directive it auto-probes for a bound Copilot session and falls back to Codex.

Can the reviewer be the same model family as the executor?▼

No. The router enforces opposite-family reviewer selection, for example an Anthropic executor gets an OpenAI reviewer. Same-family or unknown-family identity cannot acquit and results in a REVIEW_UNAVAILABLE error.

What is the difference between medium, hard, and nightmare review difficulty?▼

Medium uses standard MCP-based review where the executor controls reviewer context. Hard adds persistent reviewer memory and a debate protocol. Nightmare lets the reviewer read the repo directly via codex exec and independently verify that code matches claims.

What happens if the review loop is interrupted by context compaction?▼

State is persisted to review-stage/REVIEW_STATE.json after every round, including run_id, round, threadId, and backend. On restart, in-progress state younger than 24 hours resumes from the next round; older or completed states trigger a fresh run.

When should I not wrap this skill in a scheduler or cron job?▼

Never wrap it in /loop, /schedule, or CronCreate because it already loops internally and the reviewer carries memory across rounds. An external timer resets reviewer memory each tick, producing no new signal at full token cost.