Loop On Ci

by cursorccb5507cec15No license10K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated today

Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks.

Instructions onlyDevOps & Cloud
AI-generated overview

Watches pull request CI checks with gh and iterates on failures until all required checks pass.

What it does
This skill defines a workflow for monitoring the checks attached to a pull request and fixing failures until they are green. It resolves the active PR, inspects the current check set, diagnoses failures, watches pending checks with fail-fast, and re-checks after every push. It produces a CI status report, a failure summary with the fixes applied, and the PR URL once checks pass.
When to use it
Use it when you need to watch a branch or pull request and iterate on CI failures until all required checks are green. It is suited to repeated push-and-verify cycles on a PR.
Requirements
Requires the GitHub CLI (gh) authenticated against the repository, with network access to GitHub. It is instructions only and ships no scripts.

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

bash
# Resolve the active PRgh pr view --json number,url,headRefName
# Inspect all attached checksgh pr checks --json name,bucket,state,workflow,link
# Watch pending checks and fail fastgh pr checks --watch --fail-fast
# GitHub Actions logs, when the failing check links to a GHA rungh 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

Source and attribution

Source:cursor/pluginsincursor-team-kit/skills/loop-on-ciat commitccb5507

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal