ci-watch

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.

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.

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.

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.

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.

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.