monitor-ci

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

1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/G9000/animaOS-SWARM --skill monitor-ci-g9000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitor-ci
Source: https://github.com/G9000/animaOS-SWARM/tree/main/.agents/skills/monitor-ci
Command: npx skills add https://github.com/G9000/animaOS-SWARM --skill monitor-ci-g9000

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Monitor Nx Cloud CI pipeline executions and reduce manual intervention by orchestrating automated self-healing fixes, local verification, and safe push workflows when CI fails.

Core Features & Use Cases

  • Continuous CI Monitoring: Polls Nx Cloud CI attempts, detects progress, and reports status changes with configurable verbosity and timeouts.
  • Self-Healing Orchestration: Integrates with Nx Cloud self-healing via MCP calls to apply, reject, or request environment reruns and coordinates local verification and fixes when needed.
  • Safe Local Fix Workflow: Provides gated local verification, commit/push flows, and explicit safeguards for environment failures, throttling, and cycle limits.
  • Use Case: Automatically watch the current branch's CI, attempt verified fixes via Nx Cloud, run local verification for non-e2e failures, and push safe changes only when gate checks allow.

Quick Start

Use monitor-ci to watch the current branch's Nx Cloud CI and attempt automated self-healing fixes as configured.

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 pipeline monitoring and self-healing?

Automated Nx Cloud CI monitoring and self-healing is achieved by polling CI attempts, detecting status changes, and orchestrating fixes via MCP tools. This process applies verified local fixes and gated push workflows to safely resolve failing CI attempts in Nx-based repositories.

What is the best way to handle failing Nx Cloud CI attempts automatically?

Handling failing Nx Cloud CI attempts automatically involves applying self-healing fixes, running local verification for non-e2e failures, and using gated commit and push flows. Safeguards for environment failures, throttling, and cycle limits ensure safe automated remediation.

Do I need nx.json and git context to run continuous CI monitoring?

Yes, continuous CI monitoring requires access to repository git context and nx.json Nx Cloud identifiers. The orchestration also depends on the ci_information and update_self_healing_fix MCP tools, alongside deterministic Node scripts for state management and decision processing.

How does the self-healing workflow verify fixes before pushing to an Nx repository?

The self-healing workflow verifies fixes by running local checks for non-e2e failures before allowing any code changes. It uses a gated push workflow that only commits and pushes safe changes when local gate checks pass, explicitly safeguarding against environment reruns and cycle limits.

Can I use this CI monitoring automation for non-e2e test failures in Nx?

Yes, CI monitoring automation supports local verification specifically for non-e2e failures. When Nx Cloud CI fails, it orchestrates local fix application, verifies the changes, and requests environment reruns only when necessary, preventing unsafe pushes to the repository.

What are the limitations of automated CI self-healing for Nx Cloud pipelines?

Automated CI self-healing limitations include explicit safeguards for environment failures, throttling, and cycle limits. It restricts automated local verification to non-e2e failures and enforces gated push workflows, preventing unverified changes from being committed to Nx-based repositories.