monitor-ci

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

1.4k|245|Updated Jun 18, 2018
One-click install
npx skills add https://github.com/nrwl/nx-console --skill monitor-ci
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitor-ci
Source: https://github.com/nrwl/nx-console/tree/main/.cursor/skills/monitor-ci
Command: npx skills add https://github.com/nrwl/nx-console --skill monitor-ci

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the monitoring of Nx Cloud CI pipelines and orchestrates self-healing fixes, reducing manual intervention and speeding up feedback loops for developers.

Core Features & Use Cases

  • Continuous Nx Cloud CI monitoring with automatic health checks and status reporting.
  • Self-healing orchestration by spawning the ci-watcher subagent to poll CI status and decide next steps.
  • Robust wait-mode and new-CIPE detection to reliably track updates and avoid stale data.
  • Pre-CIPE failure handling (No-new-CIPE) with optional auto-fix workflows to attempt lockfile or environment fixes.
  • Configurable timeouts, branch detection, and verbosity to tailor monitoring to the team’s needs.
  • Nx Cloud connection verification to prevent false positives and guide remediation if disconnected.

Quick Start

Start monitoring CI for a branch using: monitor-ci --branch <branch> with default settings. To wait for a new CI, use the WAIT MODE prompt shown after a triggering action.

Frequently Asked Questions about monitor-ci

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

FAQPage Schema
How do I automate monitoring of Nx Cloud CI pipelines?

Monitor Nx Cloud CI pipelines automatically using monitor-ci, which continuously polls CI status, detects failures, and orchestrates self-healing fixes. Start with `monitor-ci --branch <branch>` to begin monitoring a specific branch with default settings.

Can monitor-ci automatically fix CI failures in Nx workspaces?

Yes, monitor-ci automates self-healing by spawning a ci-watcher subagent that polls CI status and decides next steps. It handles pre-CIPE failures with optional auto-fix workflows for lockfile or environment issues, plus applies and pushes fixes locally.

What happens when Nx Cloud CI detects no new CIPE or encounters pre-CIPE issues?

Monitor-ci implements robust wait-mode and new-CIPE detection to track updates reliably. For pre-CIPE failures (No-new-CIPE), it triggers optional auto-fix workflows and waits for the next CI cycle before retrying.

Does monitor-ci work with Nx workspaces across different CI environments?

Monitor-ci applies to Nx workspaces using Nx Cloud across CI failures and retries, with configurable timeouts, automatic branch detection, and MCP interactions to adapt to your team's CI workflow.

What prerequisites do I need to use monitor-ci for CI automation?

You need an Nx workspace with Nx Cloud connected and active. Monitor-ci verifies the connection before monitoring; if disconnected, it guides you through remediation to prevent false positives.

How does monitor-ci reduce manual intervention in DevOps workflows?

Monitor-ci automates health checks and status reporting across CI pipelines, eliminating manual polling. Its configurable monitoring loop and self-healing orchestration speed up feedback loops and fix deployment without developer intervention.