loop-on-ci
Skill7 starsChanged 3 months agoMITView on GitHub
Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks.
5 other projects use a version of this, 4 of them edited.
Adopted by
Most recently taken up by
- ArchitektApx/cursor-skills-for-claudeedited, first seen Nov 1, 2026
- jimyag/dotfilestheir own version, first seen Oct 8, 2026
- dhanji4U/skillsedited, first seen Oct 2, 2026
- ElyzeSolutions/skillsedited, first seen Aug 6, 2026
- cogine-ai/cogine-dev-skillsetedited, first seen Jun 25, 2026
Used with
Projects with it also use make-pr-easy-to-review.
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.
jaydubya818Skillmake-pr-easy-to-review
Use when a correct pull request needs clearer history, description, or reviewer guidance.
Also in 3 projects that use this
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 4
- cogine-ai/cogine-dev-skillset★ 4100% same
- dhanji4U/skills★ 288% same
- ElyzeSolutions/skills★ 1100% same
- ArchitektApx/cursor-skills-for-claude★ 0100% same
Wrote their own version · 1
- jimyag/dotfiles★ 11same 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 repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- browser-useSkill
- code-reviewSkill
- implementSkill
- leadSkill
- mermaidSkill
- run-smoke-testsSkill
- tddSkill
- to-ticketsSkill
- unslopSkill
The file
We split this skill into the rules it gives an agent
9 rules. 5 are common, 0 are distinctive, and 4 are very specific to this project.
5
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
4
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
- Very specific: line 12
Use gh pr checks as the source of truth.
- Common: line 20
If checks already failed, diagnose those failures first.
- Very specific: line 22
If checks are pending, watch with gh pr checks --watch --fail-fast.
- Common: line 24
After each push, re-check the full PR check set and repeat until green.
- Common: line 44
Keep each fix scoped to a single failure cause when possible.
- Very specific: line 46
Do not bypass hooks (--no-verify) to force progress.
- Common: line 48
If the failure is clearly unrelated to the PR and appears fixed on main, merge latest main instead of bloating the PR with unrelated fixes.
- Common: line 50
If failures are flaky, retry once and report flake evidence.
- Very specific: line 64
Never merge. Never gh pr merge.
“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 on CI
Trigger
Need to watch a branch or pull request and iterate on CI failures until all required checks are green.
Use gh pr checks as the source of truth. It includes all PR-attached checks, while gh run list only covers GitHub Actions.
Workflow
- Resolve the PR for the current branch.
- Inspect current PR checks before waiting.
- If checks already failed, diagnose those failures first.
- If checks are pending, watch with
gh pr checks --watch --fail-fast. - After each push, re-check the full PR check set and repeat until green.
Commands
# Resolve the active PR
gh pr view --json number,url,headRefName
# Inspect all attached checks
gh pr checks --json name,bucket,state,workflow,link
# Watch pending checks and fail fast
gh pr checks --watch --fail-fast
# GitHub Actions logs, when the failing check links to a GHA run
gh run view <run-id> --log-failedGuardrails
- Keep each fix scoped to a single failure cause when possible.
- Do not bypass hooks (
--no-verify) to force progress. - If the failure is clearly unrelated to the PR and appears fixed on main, merge latest main instead of bloating the PR with unrelated fixes.
- If failures are flaky, retry once and report flake evidence.
- Re-run
gh pr checks --json name,bucket,state,workflow,linkafter every push; the check set can change.
Output
- Current CI status
- Failure summary and fixes applied
- PR URL once checks are green
Factory override
Never merge. Never gh pr merge. Only the dispatched PR.
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.