做什么
迭代工人-审查员周期,该周期培养一名评论员副代理人,对工作1-10进行评分,提供可采取行动的反馈,然后修订,直至达到质量门
技能库 智客分类:写作与研究 review-loop
迭代工人-审查员周期,该周期培养出评论员子代理人来给工作1-10打分并提供可操作的反馈,然后修改直至达到质量门. 在执行特性时使用,写出规格,审查已存在的代码,或者完成质量重于速度的任何任务. 触发短语:"使用审查-loop","polish this","透出这个","/review-loop","review with re反馈循环".
官方网址:skills.sh
先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。
迭代工人-审查员周期,该周期培养一名评论员副代理人,对工作1-10进行评分,提供可采取行动的反馈,然后修订,直至达到质量门
-用户说"使用审查-loop","使用这个","通过这个","通过这个","/审查-loop"
按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:Review Loop、Quick Start、When to Use、When NOT to Use、Defaults、Model Selection。 其中含规范建议的小节:分步指令。
文件分析:这是一份仅含 SKILL.md 的指令型技能,代理激活后整份正文进入上下文。
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".
Review LoopQuick StartWhen to UseWhen NOT to UseDefaultsModel SelectionUser OverridesThe ProcessStep-by-StepStep 1: Do the WorkStep 2: Spawn Reviewer SubagentWhat was done
来源分类:skills.sh agent-skill
namereview-loopdescription具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗
先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。
复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。
把 Agent Skill「review-loop」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-586fe7d1cbbb6adc-%E5%AE%A1%E6%9F%A5%E5%BE%AA%E7%8E%AF.html 请存为 .cursor/skills/review-loop/SKILL.md 或 .claude/skills/review-loop/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。
npx skills add 'https://github.com/2dmurali/review-loop-skill' --list
npx skills add 'https://github.com/2dmurali/review-loop-skill' --skill 'review-loop'
CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。
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.
"implement X, use review-loop" or "run review-loop on the file I just wrote"| 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) |
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. If the reviewer is weaker than the worker, it cannot properly critique complex logic or catch subtle regressions.
| Task Complexity | Worker Capability | Reviewer Capability | Rationale | |----------------|--------|----------|-----------| | Simple/mechanical (CRUD, formatting, boilerplate) | Fast / Lightweight | Balanced | Lightweight worker is fast, balanced reviewer easily catches issues | | Standard (features, refactors, docs) | Balanced | Balanced | Good mix of cost, speed, and quality | | Complex (multi-file, integration, design) | Balanced | Advanced / Reasoning | Advanced reviewer catches subtle architecture issues, balanced worker can implement them | | Very complex (security, quant, distributed systems) | Advanced / Reasoning | Advanced / Reasoning | Both need full context and reasoning power. Reviewer MUST match worker power. |
The golden rule: The worker must be smart enough to ACT on the reviewer's feedback. If the reviewer says "fix the race condition with a channel-based semaphore" and the worker can't reason about concurrency, the loop won't converge.
Escalation signal: If score doesn't improve after 2 consecutive loops with the same feedback, the worker model is too weak. Escalate:
Default behavior: Since you (the main agent) ARE the worker, spawn a reviewer subagent that matches or exceeds your current capability based on the task:
Users can override any default inline with their request. Parse these naturally:
"implement X with review-loop, quality gate 9, use advanced model for review, max 5 loops"
"polish this, 2 loops minimum, gate at 8"
"run review-loop with fast reviewer, max 2 loops"
"use review-loop, reasoning reviewer, quality gate 9, min 3 max 6"
Parsing rules:
flowchart TD
A[Do the work] --> B[Spawn reviewer subagent]
B --> C{Min loops met?}
C -- no, always continue --> E[Revise based on feedback]
C -- yes --> D{Score >= quality gate?}
D -- yes --> F[Final polish pass]
D -- no --> G{Max loops reached?}
G -- yes, stop anyway --> F
G -- no --> E
E --> B
F --> H([Done])
Complete the task as you normally would. Write the code, create the spec, implement the feature. Don't hold back — produce your best first attempt.
Use the Agent tool to dispatch a reviewer. The reviewer must:
Reviewer prompt template:
You are a critical reviewer. Score the following work 1-10 and provide specific, actionable feedback.
## What was done
{brief description of the task}
## Review criteria
{task-specific criteria — what matters for THIS task}
Examples of well-written criteria:
For a REST API endpoint:
- Correct HTTP status codes used
- Input validation present on all parameters
- Auth enforced; no unauthenticated access
- No N+1 query patterns
For a design doc:
- Problem statement is unambiguous
- Alternatives considered with trade-offs
- No hand-waving on implementation complexity
- Success metrics are measurable
For a data pipeline:
- Idempotent — safe to re-run
- Schema changes handled gracefully
- Failure modes documented
- PII handling addressed
## Instructions
1. Read the work carefully
2. Score 1-10 where:
- 1-3: Fundamentally broken or missing major requirements
- 4-6: Works but has significant issues
- 7-8: Good, minor issues only
- 9-10: Excellent, ready to ship
3. List specific issues with file:line references where applicable
4. For each issue, explain WHY it matters and WHAT to fix
5. Do NOT be polite — be honest and direct
6. State your score clearly as "Score: N/10"
## Files to review
{paste file contents or list file paths with relevant excerpts}
From the reviewer response, extract:
Report to the user:
Loop {N}/{max}: Score {X}/10
- {summary of key feedback points}
In this order:
Address the reviewer's feedback. Fix Critical and Important issues. Minor issues are optional. Then go back to Step 2.
Important: Each revision should be targeted. Don't rewrite everything — fix what the reviewer flagged. Maintain a mental list of ALL prior feedback to avoid regressions.
Once the loop exits (quality gate met or max loops hit):
| Task Type | Reviewer Should Focus On | |-----------|--------------------------| | Code | Correctness, edge cases, error handling, readability, no security issues | | Spec/Design | Completeness, feasibility, no hand-waving, implementability | | Refactor | No behavior changes, no regressions, cleaner than before | | Writing | Clarity, structure, audience-appropriate, no fluff | | Bug fix | Root cause addressed, regression test exists, no side effects | | Infrastructure / IaC | Idempotency, least privilege, no hardcoded secrets, destroy safety | | Database migration | Reversibility, index strategy, data loss risk, performance at scale | | API design | Backward compatibility, auth, versioning, error contract | | Test suite | Edge case coverage, no test interdependency, meaningful assertions |
User gives a task + says to use review-loop. You do the work AND run the review loop.
User: "Implement the caching layer. Use review-loop, quality gate 8."
You:
1. Implement caching layer
2. Spawn reviewer → Score 6, feedback: missing eviction, no TTL
3. Revise: add eviction + TTL
4. Spawn reviewer → Score 8, feedback: minor naming nit
5. Final polish, done
User already did work or you already did work. Just run the review loop on what exists.
User: "Run review-loop on the auth module I just wrote"
You:
1. Read the auth module
2. Spawn reviewer → Score 5, feedback: SQL injection, no rate limiting
3. Fix: parameterize queries, add rate limiter
4. Spawn reviewer → Score 8, approved
5. Done
Never:
If reviewer is wrong:
--- Review Loop: {task name} ---
Loop 1/4: Score 6/10
Reviewer: Missing input validation, no error handling for network timeout,
function too long (80 lines).
Action: Fixing all three issues.
Loop 2/4: Score 8/10
Reviewer: Clean. Minor: variable name `d` could be more descriptive.
Action: Quality gate met (8 >= 8). Final polish.
Result: 8/10 in 2 loops. Done.
MIT — free to use, adapt, and redistribute with any AI tool or platform. Attribution appreciated. Contributions welcome.
写作与研究
从文本中删除 AI 生成的写入标记 。 编辑或审查文本时使用,使其声音更自然和人文写作. 基于维基百科的全面"AI写作的标志"指南. 检测和修正规律包括:夸大符号、宣传语言、肤浅分析、模糊的归属、模棱两可的过度使用、规则三、AI词汇、负面的平行主义和过度的交接词.
写作与研究
OpenClaw 的默认网络搜索 。 搜索网络跨越了10个引擎——Google,Reddit,GitHub,arXiv,Hacker News等——使用Prismfy. 包括免费等级,不需要信用卡。 包括用于网络搜索、配额检查和引擎/时间/域过滤器的捆绑 " search.sh …
写作与研究
监控博客和RSS/Atom的种子.
写作与研究
AI-优化了使用Tavily Search API的网络搜索. 需要全面网络研究,时事搜索,域名特定搜索,或AI生成的回答摘要时使用. Tavily是LLM消费的优化型,具有清洁的结构化结果,答案生成,以及原始内容提取. 最适合研究任务、新闻查询、实况调查和收集权威来源.