monitor-ci

Monitor Nx Cloud CI pipelines across branches and PRs using automated CI status tracking, which provides real-time build failure visibility and coordinates self-healing remediation workflows to reduce manual triage.

Yes, you can automatically initiate self-healing fixes for CI build failures. The workflow uses a subagent to coordinate remediation, applying configurable safeguards for cycles, timeouts, and auto-fix behavior to prevent runaway actions.

Wait-mode handling pauses the self-healing workflow to safely wait for a new CI attempt before taking further action. It includes fallback guidance for scenarios where no new CI attempt is triggered or environment issues occur.

The CI monitoring workflow provides configurable timeouts and cycle limits to constrain auto-fix behavior. These safeguards prevent infinite self-healing loops and ensure automated remediation stops when limits are exceeded.

When no new CI attempt is detected, the self-healing workflow provides guidance and fallbacks for no-new-CI-Attempt scenarios and environment issues, ensuring the pipeline does not hang indefinitely without actionable feedback.

Yes, Nx Cloud is required because the CI monitoring skill specifically tracks Nx Cloud CI pipelines. You need an active Nx Cloud configuration to enable branch tracking and coordinate self-healing fixes for build failures.