monitor-ci

Monitor Nx Cloud CI pipeline executions and coordinate self-healing actions.

14|5|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/TheCardGoat/lorcana-simulator --skill monitor-ci-thecardgoat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitor-ci
Source: https://github.com/TheCardGoat/lorcana-simulator/tree/main/.opencode/skills/monitor-ci
Command: npx skills add https://github.com/TheCardGoat/lorcana-simulator --skill monitor-ci-thecardgoat

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It helps you continuously monitor Nx Cloud CI pipeline runs and automatically apply or guide self-healing fixes when failures are deterministic and safe to resolve.

Core Features & Use Cases

  • Nx Cloud CI polling with self-healing awareness: Tracks CI Attempt status, self-healing state, verification state, and failure classification to decide whether to wait, poll, or take action.
  • Action orchestration for fixes: Applies verified fixes via MCP, or runs a controlled local verify/enhance workflow when tasks need additional confidence.
  • Safety guardrails and budgeting: Enforces cycle limits, local-fix budgets, and explicit decision codes to prevent destructive or wasteful retries.

Quick Start

Run the skill with the instruction: monitor ci for the current branch.

Frequently Asked Questions about monitor-ci

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

FAQPage Schema
How do I automate CI pipeline recovery for broken PRs?

You can automate CI pipeline recovery by polling Nx Cloud attempt statuses, classifying failures, and orchestrating verified fixes via MCP tool calls to automatically repair broken PRs.

What is self-healing CI monitoring and how does it decide when to apply fixes?

Self-healing CI monitoring continuously tracks CI execution attempts, verification states, and failure classifications to decide whether to wait, apply a fix via MCP, or run a local verify workflow.

Do I need an Nx Cloud workspace to run automated CI self-healing?

Yes, automated CI self-healing requires a connected Nx Cloud workspace to poll pipeline executions, track CI status, and coordinate automated recovery actions for your branch or PR workflows.

How to prevent unsafe retries when applying CI self-healing fixes?

You can prevent unsafe retries by enforcing cycle limits, local-fix budgets, and explicit decision codes that act as safety guardrails against destructive or wasteful automated pipeline recovery operations.

Why does my CI monitoring workflow wait instead of applying a fix to a failed pipeline?

Your CI monitoring workflow waits instead of applying a fix because deterministic polling logic evaluates the CI attempt status, self-healing state, and verification results before safely proceeding with any corrective action.