skills.rest
ZHLX2005
ZHLX2005COMMUNITY
Explore all skills by this author →
GitHub

gh-ci-monitor

Monitors GitHub Actions CI builds until completion and retries failed runs.

3|1|Updated Apr 14, 2026
Search Tags:#automation#github actions#pipeline#gh cli#failure diagnosis#ci monitoring#build retry
One-click install
npx skills add https://github.com/ZHLX2005/sl --skill gh-ci-monitor-zhlx2005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gh-ci-monitor
Source: https://github.com/ZHLX2005/sl/tree/main/skills/gh-ci-monitor
Command: npx skills add https://github.com/ZHLX2005/sl --skill gh-ci-monitor-zhlx2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually polling GitHub Actions to check whether a CI build succeeded or failed wastes developer time and delays feedback. This Skill continuously monitors pipeline status, notifies you when the build completes, diagnoses failures, and can automatically retry failed runs. ## Core Features & Use Cases - Continuous Build Monitoring: Uses a persistent monitor on gh run list to track the latest workflow run until it reaches a completed state, without manual sleep-based polling. - Failure Diagnosis: Inspects run logs with gh run view --log and greps for errors, Gradle build details, and annotations to identify why a build failed. - Automatic Retry Handling: Reruns failed builds via gh run rerun or re-triggers PR builds, distinguishing between code errors and transient issues like stuck Gradle daemons. - Use Case: After pushing code that triggers a GitHub Actions workflow, ask the assistant to monitor the pipeline; you get notified when the build succeeds (with artifact info such as an APK) or a failure analysis with a retry option. ## Quick Start Ask the assistant to monitor the current CI pipeline and notify you when the GitHub Actions build succeeds or fails.

Frequently Asked Questions about gh-ci-monitor

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

FAQPage Schema
How do I monitor a GitHub Actions build until it finishes?▼

Use gh run list --limit 1 to check the latest run status, then set up a persistent monitor on that command so you are notified when the state changes to completed. Avoid sleep-based polling loops, since the monitor notifies on status changes automatically.

How to retry a failed GitHub Actions workflow run?▼

Run gh run rerun <run_id> to re-trigger the failed workflow. For pull request builds, you can also check out the PR and push again to create a new run. Fix code errors first before retrying.

How do I find why a GitHub Actions build failed?▼

Use gh run view <run_id> --log and grep for patterns like FAILURE or error to isolate the failing step. You can also grep around Gradle output or view annotations with gh run view to see warnings and errors.

Why does my CI monitor stop before the build completes?▼

A monitor stream ending only means polling stopped, not that the build finished. Check gh run list again to confirm the actual run status, and restart monitoring if the build is still in progress.

What should I do when a Gradle build times out in CI?▼

A timeout with no response often indicates a stuck Gradle daemon rather than a code problem. In that case, rerun the build directly with gh run rerun instead of changing code.

Related Skills

Explore More Software Engineering Skills→
openheronopenheron
10

github

Manage GitHub issues, pull requests, and workflow runs via the gh CLI.

Official
Intermediate
Loot-LabsLoot-Labs

post-pr-to-slack

Fetch pull request details via gh pr view and post summaries to Slack.

Official
Intermediate
googlegoogle
291

Push to GitHub

Run unit tests and lint checks before pushing changes to GitHub.

Official
Intermediate
nudgebeenudgebee
381

pr-backlog

Monitor GitHub pull requests for review requests and notify via macOS or Slack.

Official
Intermediate