monitor-ci

Automate Nx Cloud CI monitoring by running /monitor-ci to spawn a dedicated subagent that polls pipeline status, decides actions, and manages self-healing retries automatically. It coordinates fixes across branch scenarios and environment issues without manual intervention.

Self-healing CI is an automated mechanism that monitors Nx Cloud pipelines, detects failures, and triggers retries or fixes. A dedicated subagent continuously polls CI status, evaluates failure conditions, and applies corrective actions to resolve branch and environment issues.

Yes, Nx Cloud configuration in nx.json is required to monitor CI pipelines. You also need a running repository and the ability to spawn a ci-monitor-subagent for polling. Default settings for max cycles, timeouts, and verbosity are provided but can be overridden.

Yes, you can override default settings for max cycles, timeouts, and verbosity when monitoring CI status. The Skill provides sensible defaults for the polling subagent but allows user overrides to customize retry behavior and monitoring duration.

The self-healing monitor handles CI failures across branch monitoring scenarios and environment issues. It polls Nx Cloud pipeline status, identifies failure conditions, and coordinates retry attempts by spawning a subagent to decide and manage corrective actions.

CI monitoring may stop if max cycles or timeout limits are reached during polling. The subagent manages retries within these configured bounds, and exceeding default or overridden limits will halt the self-healing process to prevent endless retry loops.