monitor-ci

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

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/lhew/movingday --skill monitor-ci-lhew
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitor-ci
Source: https://github.com/lhew/movingday/tree/main/.agents/skills/monitor-ci
Command: npx skills add https://github.com/lhew/movingday --skill monitor-ci-lhew

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Nx Cloud CI pipelines can stall or fail, causing wasted developer time. This skill provides continuous monitoring and orchestration to keep CI progress moving and guide remediation.

Core Features & Use Cases

  • Orchestrates monitoring of Nx Cloud CI pipelines and triggers self-healing workflows.
  • Spawns specialized subagents to fetch CI information, assess states, and apply fixes.
  • Supports policy-driven gating and cycle limits to prevent runaway processes.

Quick Start

Start monitoring by telling the agent to watch the current branch's CI status and apply self-healing when needed.

Frequently Asked Questions about monitor-ci

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

FAQPage Schema
How do I monitor Nx Cloud CI pipelines and apply self-healing fixes?

You can monitor Nx Cloud CI pipelines by instructing the orchestrator to watch your current branch status, spawning subagents to fetch CI data, assess states, and apply self-healing fixes automatically.

What is automated CI self-healing and how does it minimize pipeline downtime?

Automated CI self-healing continuously monitors pipeline states and triggers remediation workflows to resolve stalls or failures, minimizing wasted developer time and keeping CI progress moving without manual intervention.

How do I start monitoring a specific branch's CI status in an Nx workspace?

To start monitoring a specific branch, tell the agent to watch the current branch's CI status within your Nx workspace, and it will apply self-healing workflows when needed based on policy-driven gating.

Can I use policy-driven gating and cycle limits to prevent runaway CI automation?

Yes, you can enforce policy-driven gating and cycle limits to prevent runaway processes, ensuring the self-healing orchestrator operates within safety guardrails and does not execute uncontrolled remediation actions.

Does this Nx Cloud monitoring tool work with workspaces relying on Nx Cloud for CI?

Yes, this applies across Nx workspaces that rely on Nx Cloud for CI, supporting branch-specific monitoring and auto-remediation workflows to coordinate self-healing fixes effectively.

Why does my Nx Cloud CI pipeline stall and how can an orchestrator fix it?

Nx Cloud CI pipelines can stall or fail due to various build issues, but an orchestrator can spawn specialized subagents to assess states and apply self-healing fixes to minimize downtime.