loop-review
Skill166 starsChanged 5 months agoMITView on GitHub
Run OpenIAP's complete latest-main-to-production loop: review-self, PR review and merge, exact-main cleanup, sequential stable releases, release-note verification, and production docs deployment.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- microlinkhq/skillstheir own version, first seen Nov 1, 2026
- rossinsilico/loop-anythingtheir own version, first seen Oct 11, 2026
- VioletScar-Hui/Build_Great_Looptheir own version, first seen Oct 9, 2026
- getlago/lago-fronttheir own version, first seen Oct 8, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- getlago/lago-front★ 163same name
- microlinkhq/skills★ 4same name
- VioletScar-Hui/Build_Great_Loop★ 2same name
- rossinsilico/loop-anything★ 0same name
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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/openiap-ssot.mdcCursor rule
- add-showcase-appSkill
- e2e-matrix-runner-appleSkill
- e2e-matrix-runner-googleSkill
- e2e-matrix-runnerSkill
- generate-docSkill
- github-labelsSkill
- iapkit-e2e-martieSkill
- iapkit-e2e-petguSkill
- opencollective-stewardSkill
- openiap-workflowsSkill
- rebase-mainSkill
- review-selfSkill
- ship-releaseSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 11
Use Claude Code's matching skills or commands for each delegated phase:
- Distinctive: line 26
Do not merge until the canonical exact-head clean gate is satisfied, and stop without merging when the canonical device-regression gate …
“Common” is measured: kept by at least 6 in 10 of the 4 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
Loop Review (Claude Code)
The canonical workflow lives in .codex/skills/loop-review/SKILL.md. Read that
file first and follow it fully.
Use Claude Code's matching skills or commands for each delegated phase:
/review-selffor pre-PR stabilization, and for exact-head fallback review only when Codex is unavailable too —review-prruns the Codex fallback first./commit --all --prfor commit, push, PR, labels, and preview./review-pr <PR>for review threads, CodeRabbit, CI polling, and cleanup./e2e-testsfor the device-regression gate — hand back to the user to run it rather than merging, since it needs real devices and store accounts./ship-releasefor affected-only sequential stable publication, registry verification, release-note verification, and production docs deployment./generate-docfor the release card the PR carries and its expected package links.ScheduleWakeupfor every five-minute re-entry; never use a shell sleep loop.
Do not merge until the canonical exact-head clean gate is satisfied, and stop
without merging when the canonical device-regression gate applies. After merge,
confirm branch deletion, switch to main, fast-forward with no tag fetch, and
verify exact clean main before invoking /ship-release.
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.