monitor-ci

Name: monitor-ci
Availability: InStock
Author: ngx-signal-forms

Monitor Nx Cloud CI pipelines and apply self-healing fixes.

3|2|Updated Oct 9, 2025

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

Ready to run

npx skills add https://github.com/ngx-signal-forms/ngx-signal-forms --skill monitor-ci-ngx-signal-forms

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates monitoring of Nx Cloud CI pipelines and coordinates self-healing fixes to reduce manual intervention and speed up CI feedback loops.

Core Features & Use Cases

Spawns and manages a ci-monitor-subagent to poll CI status and drive decision making.
Handles a wide range of CI states and self-healing flows, including wait mode and auto-fix workflows.
Provides configurable defaults (max cycles, timeouts, verbosity) and clear user guidance for progressing or halting monitoring.

Quick Start

Trigger the monitor-ci skill to start observing your Nx Cloud CI and automatically apply self-healing fixes when available.

Frequently Asked Questions about monitor-ci

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

FAQPage Schema

How do I automate Nx Cloud CI monitoring and apply self-healing fixes?▼

Automated Nx Cloud CI monitoring uses a dedicated subagent to poll pipeline status and trigger self-healing workflows, preemptively resolving failures to reduce manual intervention and speed up feedback loops.

What are self-healing workflows in CI pipelines and how do they handle environment issues?▼

Self-healing workflows in CI pipelines detect states like environment issues or stalled attempts and automatically apply configured fixes. They operate within defined cycles to preemptively resolve failures without manual input.

Can I configure timeout and cycle limits for CI monitoring automation?▼

Yes, CI monitoring automation supports configurable defaults for max cycles, timeouts, and verbosity. These settings control how long the system polls and attempts self-healing fixes before halting.

What happens when there are no new CI attempts during an automated monitoring cycle?▼

When there are no new CI attempts, the monitoring system enters a wait mode. It continues polling within the configured cycle and timeout limits until new pipeline activity is detected or limits are reached.

Does Nx Cloud CI monitoring support wait mode and auto-fix workflows simultaneously?▼

Yes, the monitoring orchestration handles both wait mode for stalled pipelines and auto-fix workflows for active failures. It tracks state and communicates with self-healing flows via defined actions to resolve issues.

When should I halt automated CI monitoring instead of continuing self-healing cycles?▼

You should halt automated CI monitoring when configured max cycles or timeouts are exceeded, or when the system provides clear user guidance indicating that self-healing flows cannot resolve the current environment issue.