/loop-on-ci
Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks.
Claude Code
$ npx -y skills add cursor/plugins --skill loop-on-ci --agent claude-code
Codex
$ npx skills add cursor/plugins --skill loop-on-ci -a codex -y
Cursor
$ npx skills add cursor/plugins --skill loop-on-ci -a cursor -y
Gemini CLI
$ npx skills add cursor/plugins --skill loop-on-ci -a gemini-cli -y
GitHub Copilot
$ npx skills add cursor/plugins --skill loop-on-ci -a github-copilot -y
OpenCode
$ npx skills add cursor/plugins --skill loop-on-ci -a opencode -y
Windsurf
$ npx skills add cursor/plugins --skill loop-on-ci -a windsurf -y
SKILL.md
loop-on-ci.SKILL.mdname: loop-on-ci
description: Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks.
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
1. Resolve the PR for the current branch. 2. Inspect current PR checks before waiting. 3. If checks already failed, diagnose those failures first. 4. If checks are pending, watch with `gh pr checks --watch --fail-fast`. 5. 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-failed
Guardrails
- 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,link` after every push; the check set can change.
Output
- Current CI status
- Failure summary and fixes applied
- PR URL once checks are green
Read more
name: loop-on-ci description: Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks.
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
1. Resolve the PR for the current branch. 2. Inspect current PR checks before waiting. 3. If checks already failed, diagnose those failures first. 4. If checks are pending, watch with `gh pr checks --watch --fail-fast`. 5. 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-failed
Guardrails
- 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,link` after every push; the check set can change.
Output
- Current CI status
- Failure summary and fixes applied
- PR URL once checks are green
Official Cursor plugins for popular developer tools, frameworks, and SaaS products. Each plugin is a standalone directory at the repository root with its own .cursor-plugin/plugin.json manifest.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about loop-on-ci.
- Which coding agents can use loop-on-ci?
- loop-on-ci installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

