| name | loop-on-ci |
| description | Inspect, plan, fix, and monitor failing CI across GitHub Actions, Buildkite, and other attached providers. Use when a user asks to debug CI, summarize a red build or PR, propose a CI fix plan, fix failing checks, retry a flaky job, or watch checks until they pass. Accepts a PR, branch, commit, build URL, or provider-specific build identifier. |
Loop On CI
Find failing checks, route them to the correct provider, diagnose root causes from logs, and either stop for plan approval or apply focused fixes until every required provider is green.
Modes
- Inspect and plan: Use when the user asks to debug, inspect, summarize, or propose a plan. Diagnose failures, present the smallest fix plan, and wait for explicit approval before editing files.
- Fix and loop: Use when the user asks to fix, retry, loop, watch, or continue until green. Apply focused edits and keep checking until green or blocked. Commit and push only when explicitly requested.
1. Resolve The Target
Accept a PR number or URL, branch, commit, Buildkite URL, pipeline and build number, or the current branch by default.
For a pull request, inspect all attached checks before choosing adapters. A single PR can use GitHub Actions, Buildkite, and other providers at the same time. Classify providers from check links and workflow metadata.
For a branch or commit without a PR, use repository CI configuration and explicit user context to identify providers. Do not guess a provider from a generic failure message.
2. Load Provider Adapters
- Read references/github-actions.md for GitHub PR checks and GitHub Actions logs.
- Read references/buildkite.md for Buildkite builds, jobs, logs, retries, and watches.
- For an unsupported provider, report its check name and details URL. State that no adapter is installed instead of pretending the logs were inspected.
