review-loop
Skill39 starsChanged 4 days agoMITView on GitHub
Retired. Implement→review work now runs as pipeline run stages (builder, reviewer with a finite fail edge to an apply-fixes stage). Load this only to find where review loops moved; it points to the pipeline docs.
62 other projects use a version of this.
Adopted by
Most recently taken up by
- mihai-dinculescu/tapotheir own version, first seen Nov 16, 2026
- MichaelHolley/cc-pluginstheir own version, first seen Nov 16, 2026
- tunnckoCore/skillstheir own version, first seen Nov 16, 2026
- DaraBoth/skilljmskilltheir own version, first seen Nov 15, 2026
- agentcrew-academy/harness-starter-kittheir own version, first seen Nov 15, 2026
- sp-hk2ldn/SKILLStheir own version, first seen Nov 15, 2026
Used with
Projects with it also use motion-design, file-pr and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
soilmassSkillmotion-design
Create animations and motion graphics using industry standards. Use when asked to animate UI elements, create video content, implement transitions, or build motion systems. Implements W3C Design Tokens, Material Design 3 baseline, and Lottie specification compliance.
Also in 5 projects that use this
tekumaraSkillfile-pr
Raise a concise pull request. Use when the user asks to raise, open, or create a PR.
Also in 3 projects that use this
owidSkillbabysit-pr
Spawn a background agent that babysits an open PR — triggers a Codex review, watches CI, judges and fixes valid findings, replies to and resolves review threads, and loops to a cap. Never merges. Trigger when the user asks to "babysit the PR", "ask for codex review(s) and watch CI", or after pushing a substantial chunk to a PR branch.
Also in 4 projects that use this
HK-hubSkillpolish
Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.
Also in 3 projects that use this
jaydubya818Skillshow-me-your-work
Use when long-running work needs an auditable decision and evidence log.
Also in 3 projects that use this
MicrosoftSkillcouncil
Convene the persona panel — six orthogonal review lenses — on a target. Cold independent fan-out, debate-to-consensus, synthesized verdict with recorded dissent and a roster manifest.
Also in 4 projects that use this
Other versions62 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 62
- didi/mpx★ 4ksame name
- mihai-dinculescu/tapo★ 877same name
- blockscout/frontend★ 310same name
- microsoft/bocpy★ 184same name
- 9thLevelSoftware/legion★ 76same name
- microsoft/Trieste★ 53same name
- revisit-studies/study★ 47same name
- timharris707/skills★ 44same name
- agentcrew-academy/harness-starter-kit★ 42same name
- spxrogers/agentsync★ 41same name
52 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- delegatus-conveyorSkill
- delegatus-orchestrationSkill
- live-log-viewer-orchestrationSkill
- llv-conveyorSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 55 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Run implement→review work as one pipeline (create_pipeline) on the board task:
- Very specific: line 22
Do not compose a review-loop stage kind.
“Common” is measured: kept by at least 6 in 10 of the 55 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Review loops moved to pipelines
Review flows and workflows are retired (docs/design/retire-flows.md), and
their engines are removed. /api/flows and /api/workflows answer 410 for
every method, and the list_flows, get_flow and flow_action tools are gone
from the tool list. Stored flows stay readable as review history in the
interface and through GET /api/review-history?project=<project>.
Run implement→review work as one pipeline (create_pipeline) on the board task:
- a builder run stage writes the change;
- a read-only reviewer run stage with a finite fail edge,
onFail: { to: "fix", maxRounds: N, onExhausted: "advance" }, N from 1 to 9; - a fix stage (builder,
mode: "apply-fixes") whosenextreturns to the reviewer, so every round gets a fresh reviewer on the new head.
Do not compose a review-loop stage kind; it exists only for stored lanes.
An approval counts for the exact head the reviewer saw. A later commit needs a
new review. A parked stage is answered with pipeline_action resolve-decision.
continue-review is always refused: the review budget is fixed when the
pipeline is created, so a budget that was too small needs a new pipeline. A
terminal advance gate re-checks the last budget fix once before the lane
completes; a failed re-check parks the lane.
Read next:
docs/review-loop.md: how a round runs and what happens when the budget is spent;docs/pipelines.md: the stage contract, edges and actions;- the
delegatus-orchestrationanddelegatus-conveyorskills for spawning and lanes.
This pointer stays while installed copies of the skill set still link it by name.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

