monitor-ci

To monitor Nx Cloud CI pipelines and auto-heal failures, invoke the tracking skill to poll pipeline status across branches and orchestrate self-healing fixes via MCP or local verification. It spawns a subagent to apply fixes and keep deployments healthy.

Self-healing CI automatically detects and resolves pipeline failures without manual intervention. For Nx Cloud, it works by spawning a subagent that continuously polls CI status across branches and applies fixes via MCP or local verification to maintain deployment health.

Yes, a connected Nx Cloud workspace is required to track CI status across branches. The monitoring skill depends on this connection to poll pipeline tasks, detect failures, and orchestrate self-healing workflows effectively.

To handle edge cases like no-new-ci or ci_no_tasks in Nx Cloud monitoring, the skill provides guided workflows with configurable limits for cycles, timeouts, and verbosity. It addresses environment issues and applies auto-fix workflows to resolve these specific CI states.

Yes, you can configure polling cycles and timeouts for CI monitoring. The skill supports configurable limits for cycles, timeouts, and verbosity to guide user interaction and control how the subagent polls Nx Cloud CI status and applies fixes.

The best way to keep Nx Cloud deployments healthy when CI fails is to use automated self-healing workflows that monitor pipeline status and apply fixes via MCP or local verification. This approach handles failures across branches with configurable timeouts and auto-fix cycles.