Poll GitHub PR CI checks until completion using gh commands.
npx skills add https://github.com/danmestas/wardrobe --skill ci-watch-danmestas
Please help me install this Agent Skill. Skill: ci-watch Source: https://github.com/danmestas/wardrobe/tree/main/skills/ci-watch Command: npx skills add https://github.com/danmestas/wardrobe --skill ci-watch-danmestas
CI-dependent workflows require monitoring external checks to determine readiness for merge or deployment, causing delays if done manually.
Invoke the skill to watch a PR's CI checks until completion.
High-intent search queries and answers about installing and using this skill.
To monitor GitHub PR CI checks until completion, the skill uses cadence-based polling via gh pr checks and gh run watch. It distinguishes flakes from real failures and returns exit code 0 when green, 1 for failure, and 8 if still pending.
Automating CI workflows for a pull request involves polling GitHub checks at specific cadences to balance timely updates with API limits. This approach gates downstream actions when CI is green and surfaces actionable failure signals if checks fail.
Yes, you can distinguish flaky CI checks from real failures by using cadence-based polling with gh run watch. The skill monitors check status over intervals to identify transient failures before reporting a final failure exit code.
Yes, the CI polling skill supports gating actions when checks are green. It returns exit code 0 upon successful completion, allowing you to trigger downstream merge or deployment workflows automatically.
GitHub PR checks show a pending status during automated polling because the CI workflows are still running. The skill uses exit code 8 to indicate this pending state, continuing to poll until all checks reach a final green or failure state.
papachongAutomate GitHub interactions from the terminal using the gh CLI.
MissTullyAutomate PR merge, CI wait, and production canary verification.
mvillmowVerify GitHub pull requests for CI checks, approvals, and merge conflicts.
cpmappstudioListen for Clerk events and route them to downstream systems.
