skills.rest
ZanzyTHEbar
ZanzyTHEbarCOMMUNITY
Explore all skills by this author →
𝕏@ZacariahHeimGitHub

loop-on-ci

Monitor pull request checks and fix CI failures until all checks pass.

3|Updated Apr 8, 2025
Search Tags:#automation#monitoring#pull request#ci#ci failures#github cli#gh pr checks
One-click install
npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill loop-on-ci-zanzythebar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: loop-on-ci
Source: https://github.com/ZanzyTHEbar/dragonarchy/tree/main/packages/opencode/.config/opencode/skills/loop-on-ci
Command: npx skills add https://github.com/ZanzyTHEbar/dragonarchy --skill loop-on-ci-zanzythebar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Waiting on CI and manually diagnosing failing pull request checks is slow and error-prone. This Skill automates the loop of watching PR checks, diagnosing failures, applying scoped fixes, and re-verifying until every required check is green. ## Core Features & Use Cases - PR Check Monitoring: Uses gh pr checks as the source of truth, covering all PR-attached checks rather than only GitHub Actions runs. - Failure Diagnosis: Inspects failing checks and pulls GitHub Actions logs with gh run view --log-failed to identify root causes. - Guardrailed Iteration: Keeps each fix scoped to a single failure cause, retries flaky checks once, and never bypasses hooks with --no-verify. - Use Case: You push a branch and open a PR, then ask the assistant to watch the checks. It detects a failing lint job, reads the logs, fixes the offending file, pushes the fix, and re-verifies until the PR is green. ## Quick Start Watch the pull request for my current branch and fix any CI 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 watch pull request checks from the command line?▼

Use gh pr checks --watch --fail-fast to stream the status of all checks attached to a pull request until they complete. The GitHub CLI reports each check's name, state, and link so you can act on failures immediately.

How do I see logs for a failing GitHub Actions check?▼

Run gh run view <run-id> --log-failed to print only the failed step logs for a workflow run. Get the run ID from the failing check's link shown by gh pr checks.

Why use gh pr checks instead of gh run list for CI status?▼

gh pr checks includes every check attached to the pull request, including third-party status checks, while gh run list only covers GitHub Actions workflows. This makes gh pr checks the reliable source of truth for merge readiness.

What should I do when a CI failure is flaky?▼

Retry the failing check once and record evidence that it is flaky, such as inconsistent pass/fail results on identical code. If failures persist and are unrelated to the PR, merge the latest main instead of adding unrelated fixes.

When should I not push fixes during CI repair?▼

Only push when the user explicitly requested CI repair or approved pushing. Never bypass commit hooks with --no-verify to force progress, and keep each fix scoped to a single failure cause.

Related Skills

Explore More Software Engineering Skills→
EtanHeyEtanHey

create-pr

Push a Git branch and create a pull request via GitHub CLI.

Community
Intermediate
Clawdi-AIClawdi-AI
4

merge-pr

Merge GitHub pull requests via squash after validating checks and branch status.

Official
Advanced
matteingmatteing
56

ci-preflight

Run the full CI suite locally to verify Elixir and TypeScript checks before pushing.

Community
Intermediate
waynebrantleywaynebrantley
1

github-workflow-doctor

Diagnose and repair failing GitHub Actions workflows by analyzing logs and applying fixes.

Community
Advanced