monitor-ci

Automated Nx Cloud CI monitoring polls branch-specific pipeline attempts, detects terminal failures, and orchestrates self-healing fixes by running local verification tasks and coordinating MCP updates. It eliminates manual polling by fetching CI information, gating local verification, and applying verified fixes via MCP updates or local commits.

Self-healing CI automation detects failed Nx Cloud CI attempts and orchestrates deterministic fixes without manual intervention. It works by polling CI status, classifying environment versus code failures, running local verification tasks, and applying fixes via MCP tools or safe local commits while respecting safety gates and cycle limits.

To set up CI polling, you need a git repository context, an Nx workspace with Nx Cloud configuration in nx.json, and MCP tools for CI information and self-healing updates. The skill periodically fetches CI attempt status, detects progress changes, and coordinates fixes for the monitored branch.

Safety gates for self-healing fixes include local verification gates, environment versus code failure classification, throttling handling, and cycle limits. These policies ensure deterministic decision logic prevents destructive or noisy actions, gating fixes before applying them via MCP or performing safe local pushes and empty commits.

Local verification is required before pushing fixes to classify environment versus code failures and ensure changes are safe. The automation runs suggested local verification tasks to gate fixes, preventing destructive actions and only applying verified self-healing fixes via MCP or pushing enhanced local fixes when appropriate.

No, CI monitoring automation requires Nx Cloud configuration in nx.json to poll branch-specific CI attempts and fetch CI information. It also requires a git repository context, MCP tools for CI information and update_self_healing_fix, and local Node scripts for deterministic decision and state management.