ci-watch

Monitor GitHub Actions CI status for pull requests and report terminal state.

3|1|Updated Oct 9, 2025

Search Tags:#automation #workflow #pull request #github actions #polling #ci

Ready to run

npx skills add https://github.com/OmniNode-ai/omniclaude --skill ci-watch

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ci-watch
Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/ci-watch
Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill ci-watch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the monitoring of Continuous Integration (CI) pipelines for pull requests, proactively addressing failures and reporting the final status to ensure code quality and faster development cycles.

Core Features & Use Cases

CI Polling: Continuously checks the status of GitHub Actions CI for a specified pull request.
Automated Fixing: Attempts to automatically fix introduced CI failures by dispatching specialized agents.
Pre-existing Failure Handling: Identifies and reports pre-existing CI failures, dispatching separate fixes without blocking the current PR.
Terminal State Reporting: Exits with a clear status (passed, capped, timeout, error) once CI reaches a conclusive state.
Use Case: A developer pushes code to a pull request. The ci-watch skill monitors the CI checks, automatically fixing any new linting errors that appear. If the CI pipeline times out or exhausts its auto-fix attempts, the skill reports this status, preventing accidental merges of broken code.

Quick Start

Use the ci-watch skill to monitor CI for PR number 123 in the org/repo repository.

Frequently Asked Questions about ci-watch

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

FAQPage Schema

How do I monitor GitHub Actions CI status for a pull request?▼

Automated CI monitoring tracks GitHub Actions status for a specific pull request using push-based eventing or shell script polling. It continuously checks pipeline states and reports terminal results like passed, capped, timeout, or error.

Can I automatically fix CI failures introduced in a pull request?▼

Yes, automated fixing attempts to resolve newly introduced CI failures by dispatching specialized agents. If the pipeline exhausts auto-fix attempts or times out, it reports the error state to prevent merging broken code.

How does CI monitoring handle pre-existing failures in GitHub Actions?▼

CI monitoring identifies and reports pre-existing GitHub Actions failures separately. It dispatches background fix tasks for these pre-existing issues without blocking the continuous integration checks or progress of the current pull request.

Does GitHub Actions CI polling work with background task dispatching?▼

Yes, GitHub Actions CI polling supports background task dispatching. It uses tiered execution paths including shell scripts to continuously check status while dispatching specialized agents to fix identified failures in parallel.

What is the best way to prevent merging pull requests with broken CI pipelines?▼

The best way to prevent merging broken CI pipelines is to monitor terminal states and enforce status reporting. Automated monitoring exits with a clear passed, capped, timeout, or error status to block accidental merges of failing code.

When should I use polling instead of push-based eventing for CI monitoring?▼

You should use polling for CI monitoring when push-based eventing is unavailable or restricted. The monitoring skill supports both tiered execution paths, allowing shell script polling to continuously check GitHub Actions status as a fallback.