monitor-ci

To monitor Nx Cloud CI pipeline status and recover failed runs, this Skill continuously watches pipeline progress across polling cycles and applies self-healing fixes. It uses deterministic state logic to coordinate verified fixes, local verification, and environment reruns automatically for Angular monorepos.

Self-healing CI recovery is a workflow that detects failed Nx Cloud runs, generates verified fixes, and applies them using controlled git gating. It removes the manual burden of interpreting failure states and deciding whether to apply, verify, reject, or rerun failed pipeline attempts in Angular monorepos.

Yes, you need Nx Cloud connectivity to use automated CI monitoring and pipeline recovery. The Skill requires Nx Cloud connectivity, deterministic polling and state scripts, and safe git gating for local verification and commit pushes to function properly across branch-level workflows.

To prevent accidental git pushes when applying CI fixes locally, this Skill uses gate checks and controlled git behavior. Safe recovery actions ensure you avoid accidental pushes, duplicate fixes, or wasted CI cycles during the self-healing workflow for Angular monorepo branches.

The best way to handle retry loops for failing Angular monorepo CI builds is using a self-healing workflow that tracks progress across polling cycles. This Skill monitors until Nx Cloud produces a verified fix, applies it, and waits for the next CI attempt automatically without manual intervention.

CI monitoring may stop applying fixes during pipeline recovery if Nx Cloud connectivity is lost or gate checks fail. The Skill relies on deterministic polling scripts and safe git gating; without proper environment setup, rejection paths or reruns cannot be coordinated correctly for Angular monorepos.