Agent skill · creative production · aiskillstore
review-loop
Iterative worker-reviewer cycle that spawns a critic subagent to score work 1-10 and provide actionable feedback, then revises until a quality gate is met. Use when implementing features, writing specs, reviewing existing code, or completing any task where quality matters more than speed. Trigger phrases: "use review-loop", "polish this", "iterate on this", "/review-loop", "review with feedback loop".
Why this skill is useful
Adds a structured iterative feedback mechanism that enhances the quality of outputs through subagent critique and revision.
What it needs
About 8k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Review Loop Iterative worker-reviewer cycle within a single session. You do the work, spawn a reviewer subagent to critique it, revise based on feedback, repeat until quality gate is met. Core principle: First drafts are never final. Iterative critique produces better output than a single pass. Platform note: This skill works best with agents that support subagent spawning. On platforms without that capability, simulate the reviewer step by opening a fresh chat context, pasting only the work product (no prior reasoning), and asking it to score 1-10 with specific feedback. Quick Start 1. Say: "implement X, use review-loop" or "run review-loop on the file I just wrote" 2. The agent does the work (or reads existing work) 3. A separate critic subagent scores it 1-10 with specific feedback 4. The agent revises and repeats until score >= 8 (default quality gate) 5. A loop summary is delivered with the final output --- When to Use User says "use review-loop", "polish this", "iterate on this", "/review-loop" Complex implementations where quality matters more than speed Design docs, specs, or technical writing Code that needs to be robust (security, data pipelines, financial logic) When user wants adversarial critique baked into the process When NOT to Use Simple fixes, quick edits, one-liner changes Tasks where tests are the quality gate (use TDD + CI instead) When the user just wants it done fast Exploratory/spike work where the goal is learning, not shipping Tasks with no clear acceptance criteria — define those first, then use review-loop --- Defaults Setting Default --------- --------- Min loops 2 Max loops 4 Quality gate 8/10 Worker model (your current model) Reviewer model (your current model or fast/balanced alternative) --- Model Selection The reviewer task evaluates logic and constraints. The worker task writes and modifies code. Pick subagent capabilities accordingly. CRITICAL RULE: The Reviewer must always be EQUAL TO or MORE POWERFUL than the Worker. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/review-loop