monitor-ci

Monitor Nx Cloud CI pipelines and orchestrate self-healing fixes via MCP.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/sneat-co/sneat-apps --skill monitor-ci-sneat-co
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitor-ci
Source: https://github.com/sneat-co/sneat-apps/tree/main/.cursor/skills/monitor-ci
Command: npx skills add https://github.com/sneat-co/sneat-apps --skill monitor-ci-sneat-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monitor Nx Cloud CI pipelines and orchestrate self-healing fixes so teams can reduce manual CI toil.

Core Features & Use Cases

  • Polls CI status via the ci-monitor-subagent and relays updates to users in real time.
  • Applies fixes through MCP when eligible, or initiates a local verification flow when needed.
  • Handles wait-mode for new CI attempts with configurable timeouts, branch auto-detection, and verbosity.
  • Exits cleanly on success, timeout, or critical failure with guidance for next steps.

Quick Start

Start monitoring the Nx Cloud CI pipeline for the current branch and automatically respond to failures with self-healing fixes.

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 failure remediation?

Automate Nx Cloud CI failure remediation by polling pipeline statuses and orchestrating self-healing fixes via subagent coordination and MCP, reducing manual intervention across branches.

What is self-healing CI monitoring and how does it work?

Self-healing CI monitoring continuously polls Nx Cloud pipelines, detects failures, and automatically generates or applies fixes through MCP, queuing repairs or initiating local verification flows when needed.

Can I configure timeouts and verbosity for CI polling?

You can configure timeouts and verbosity for CI polling to manage wait-mode handling for new Nx Cloud attempts, ensuring the monitor exits cleanly with guidance on success, timeout, or critical failure.

How do I monitor CI status across multiple branches automatically?

Monitor CI status across multiple branches automatically by enabling branch auto-detection within the polling workflow, which relays real-time updates and coordinates fixes for eligible failures.

What happens when a CI fix cannot be applied automatically?

When a CI fix cannot be applied automatically, the workflow initiates a local verification flow or queues the repair, exiting cleanly with actionable guidance for required next steps.