nx-ci-monitor

Monitor Nx Cloud CI pipelines and orchestrate self-healing fixes for NX projects.

59|14|Updated Mar 10, 2026

Search Tags:#automation #ci-cd #self-healing #nx #ci-monitor #nx-cloud

Ready to run

npx skills add https://github.com/guilhermemarketing/esc-skills --skill nx-ci-monitor-guilhermemarketing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: nx-ci-monitor
Source: https://github.com/guilhermemarketing/esc-skills/tree/main/skills/nx-ci-monitor
Command: npx skills add https://github.com/guilhermemarketing/esc-skills --skill nx-ci-monitor-guilhermemarketing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates monitoring of Nx Cloud CI pipelines and coordinates self-healing actions to reduce downtime.

Core Features & Use Cases

Nx Cloud connection guard: validates the workspace is connected before starting monitoring.
Spawns a ci-watcher subagent to poll CI status and drive decisions based on results.
Supports configurable cycles, timeouts, and verbosity for production-grade resilience.
Handles new CI detections, wait modes, and self-healing workflows to accelerate recovery.

Quick Start

Initialize monitoring by invoking nx-ci-monitor for your target branch and optional flags to customize timeouts and verbosity.

Frequently Asked Questions about nx-ci-monitor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate self-healing for Nx Cloud CI pipelines?▼

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.

What is a self-healing CI monitor and how does it reduce downtime?▼

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.

Do I need an active Nx Cloud connection before starting CI monitoring?▼

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.

How do I configure retry logic and polling cycles for Nx CI monitoring?▼

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.

What are the limitations of automating CI health checks for Nx projects?▼

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.