loop-on-ci

Monitor GitHub PR checks and iteratively fix CI failures until green.

2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill loop-on-ci-kscius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: loop-on-ci
Source: https://github.com/kscius/KS-Cursor-Orchestrator/tree/main/skills/loop-on-ci
Command: npx skills add https://github.com/kscius/KS-Cursor-Orchestrator --skill loop-on-ci-kscius

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline PR workflows by continuously monitoring CI checks and iteratively applying fixes until all required checks pass, reducing context switching and manual re-runs.

Core Features & Use Cases

  • Iterative CI failure diagnosis and remediation on GitHub pull requests.
  • Real-time monitoring of PR checks with gh pr checks --watch and early failure signals.
  • Progress reporting with current status, fixes applied, and the PR URL once all checks are green.
  • Use cases include flaky tests, slow CI pipelines, and multi-check PRs requiring coordinated fixes.

Quick Start

Watch the active PR's CI checks and iteratively fix failures until all checks are green.

Frequently Asked Questions about loop-on-ci

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically fix CI failures on GitHub pull requests?

To automatically fix CI failures on GitHub pull requests, this skill uses gh pr checks and gh run logs to diagnose failures, applies iterative fixes, and validates checks with --watch until all required statuses pass.

What is the best way to monitor slow CI pipelines and flaky tests across multiple PR checks?

Monitoring slow CI pipelines and flaky tests is handled by watching pending PR checks in real-time, catching early failure signals, and applying iterative remediation across branches and forks until all checks turn green.

Can I use gh run logs to diagnose and resolve CI failures on forked branches?

Yes, you can use gh run logs to diagnose CI failures on forked branches, as the skill guides resolution by viewing logs, pushing fixes, and re-checking the active PR across both branches and forks.

Does this iterative CI fix approach work with multi-check pull requests requiring coordinated fixes?

This iterative CI fix approach works with multi-check pull requests by continuously monitoring required checks, diagnosing coordinated failures using gh pr view, and applying fixes until all statuses are green.

How do I get progress updates when watching PR checks for iterative remediation?

You get progress updates during iterative remediation through status reporting that shows current check statuses, applied fixes, and the final PR URL once all required CI checks are validated as green.