nx-ci-monitor

To automate self-healing for Nx Cloud CI pipelines, you can configure this Skill to monitor CI runs, validate workspace connections, and orchestrate recovery workflows. It spawns a subagent to poll status and apply configurable retry logic for reliable outcomes.

A self-healing CI monitor automatically detects failing Nx Cloud pipelines and triggers recovery workflows without manual intervention. By continuously polling CI status and applying retry logic, it accelerates recovery and reduces pipeline downtime.

Yes, an active Nx Cloud connection is required. The Skill includes a connection guard that validates your workspace is properly connected to Nx Cloud before initializing any monitoring or self-healing workflows.

You can configure retry logic, polling cycles, and timeouts by passing optional flags when initializing the monitor for your target branch. These settings allow you to customize verbosity and production-grade resilience for your continuous deployment pipelines.

The automation is limited to Nx Cloud environments and requires a validated workspace connection to function. It relies on subagent polling and configured timeouts, meaning complex non-Nx CI failures or external infrastructure issues may fall outside its self-healing scope.