auto-review-loop

Automates multi-round research review cycles with independent cross-model reviewers until approval.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/hanasho744/codex --skill auto-review-loop-hanasho744
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auto-review-loop
Source: https://github.com/hanasho744/codex/tree/main/.agents/skills/auto-review-loop
Command: npx skills add https://github.com/hanasho744/codex --skill auto-review-loop-hanasho744

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Research work needs rigorous, adversarial review before submission, but manual review cycles are slow and self-review lacks independence. This Skill runs an autonomous review → fix → re-review loop with an independent reviewer from a different model family, stopping only when a policy-approved positive assessment is reached or the round limit is hit. ## Core Features & Use Cases - Autonomous Review Loop: Iterates review, fix implementation, and re-review up to 4 rounds, stopping when score >= 6/10 and verdict is "ready" or "almost". - Multiple Reviewer Backends: Routes to Copilot CLI native rubber-duck subagent, Codex MCP, manual review MCP, or compatibility copilot --agent mode, with enforced opposite-family reviewer selection for independence. - Adjustable Difficulty: Medium (default MCP review), hard (reviewer memory plus debate protocol), and nightmare (reviewer reads the repo directly via codex exec with adversarial verification). - State Persistence & Recovery: Writes REVIEW_STATE.json after each round so the loop survives context compaction and can resume mid-run. - Use Case: Before submitting a NeurIPS paper draft, run the loop so an adversarial cross-family reviewer reads your claims, code, and raw results each round while the executor implements the minimum fixes until the work passes. ## Quick Start Run the auto-review-loop skill on my current paper draft and experiment results to autonomously review and fix weaknesses until it is ready for submission.

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 AI review loop on my research paper?▼

Invoke the auto-review-loop skill with your topic or scope as the argument. It reviews your claims, code, and raw results with an independent reviewer, implements the minimum fixes, and re-reviews each round until the work scores at least 6/10 with a ready or almost verdict, or 4 rounds elapse.

What reviewer backends does the auto review loop support?▼

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

How does the skill ensure reviewer independence from the executor?▼

It enforces opposite-family routing: an OpenAI executor gets an Anthropic reviewer and vice versa, derived from the model identity. Native Copilot mode verifies independence through host session events, while caller-declared identities are recorded as unverified rather than promoted to attested.

Can the review loop resume after context compaction or interruption?▼

Yes. The loop writes review-stage/REVIEW_STATE.json after every round with the run_id, round, threadId, backend, and last score. On restart, a state file younger than 24 hours with in_progress status resumes at the next round; completed or stale states trigger a fresh start.

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

Medium uses a standard MCP review where the executor controls reviewer context. Hard adds reviewer memory across rounds and a debate protocol where the executor can rebut. Nightmare lets the reviewer read the repository directly via codex exec and independently verify that code matches claims, and it requires Codex rather than the manual backend.

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 in one threadId. An external timer restarts from the top each tick with a fresh thread, resetting reviewer memory and burning tokens without new signal.