monitor-ci

Monitor Nx Cloud CI pipeline executions and orchestrate self-healing fixes for failing attempts.

Updated Apr 11, 2025
One-click install
npx skills add https://github.com/pabloimrik17/monolab --skill monitor-ci-pabloimrik17
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitor-ci
Source: https://github.com/pabloimrik17/monolab/tree/main/.opencode/skills/monitor-ci
Command: npx skills add https://github.com/pabloimrik17/monolab --skill monitor-ci-pabloimrik17

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill continuously monitors Nx Cloud CI pipeline executions, detects failures and environment issues, and coordinates verification and self-healing actions to reduce manual triage and repeated CI cycles.

Core Features & Use Cases

  • Automated Monitoring Loop: Polls Nx Cloud for CI Attempt status, self-healing progress, and verification results using a deterministic decision engine.
  • Self-healing Orchestration: Applies, rejects, or requests environment reruns via MCP tools, and can trigger local verification and safe git operations when required.
  • Gatekeeping & Safety: Enforces local-fix and environment rerun budgets, circuit-breakers, and explicit user overrides to avoid destructive or noisy actions.
  • Use Case: Monitor a failing PR on a feature branch, let the skill wait for Nx Cloud self-healing to complete, and then either auto-apply a verified fix or run safe local verification and push an enhanced fix.

Quick Start

Start monitoring the current branch's CI and attempt self-healing by issuing the command monitor ci.

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 self-healing for failing pipeline attempts?

Automate Nx Cloud CI monitoring by polling CI Attempt status and orchestrating self-healing fixes via MCP tools. The skill tracks verification results and triggers gated local git verification or automated fix applications to reduce manual triage.

What is CI self-healing orchestration and how does it work with Nx Cloud?

CI self-healing orchestration applies, rejects, or requests environment reruns for failing Nx Cloud attempts. It uses a deterministic decision engine to coordinate MCP-driven fix actions and local git workflows when verification is required.

Do I need Nx Cloud integration and MCP tools to monitor CI pipelines?

Yes, you need a workspace connected to Nx Cloud, access to ci_information and update_self_healing_fix MCP tools, and local git for verification and push workflows to monitor CI pipelines and perform self-healing actions.

How do I start monitoring CI on my current feature branch for self-healing?

Start monitoring CI on your current feature branch by issuing the command monitor ci. The skill polls Nx Cloud for CI Attempt status, waits for self-healing to complete, and then auto-applies a verified fix or runs local verification.

What safety gatekeeping limits apply to CI self-healing fixes and environment reruns?

CI self-healing safety gatekeeping enforces local-fix and environment rerun budgets, circuit-breakers, and explicit user overrides. These mechanisms prevent destructive or noisy actions during automated CI pipeline triage and fix orchestration.

What's the best way to triage failing CI cycles in an Nx workspace?

The best way to triage failing CI cycles in an Nx workspace is automated monitoring that detects failures and coordinates verification. This reduces repeated CI cycles by applying verified fixes or triggering safe local git operations.