monitor-ci

Monitor Nx Cloud CI pipelines and trigger self-healing workflows on failures.

Updated Jun 19, 2025
One-click install
npx skills add https://github.com/bennrwl/psychic-eureka --skill monitor-ci-bennrwl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitor-ci
Source: https://github.com/bennrwl/psychic-eureka/tree/main/.cursor/skills/monitor-ci
Command: npx skills add https://github.com/bennrwl/psychic-eureka --skill monitor-ci-bennrwl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monitor Nx Cloud CI pipelines and orchestrate self-healing fixes to minimize downtime and manual toil.

Core Features & Use Cases

  • Spawns and manages a ci-monitor-subagent to poll CI status in the background and relay updates to the user.
  • Enforces safety patterns and timeouts, handles retries for no-new-ci-attempts, environment reruns, and self-healing workflows.
  • Supports user overrides and configurable cycle limits to balance automation with control.

Quick Start

Run /monitor-ci to start watching the Nx Cloud CI status for the current git 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 Nx Cloud CI pipeline monitoring and reduce manual failure recovery?

Automate Nx Cloud CI pipeline monitoring by spawning a background subagent to poll pipeline status, relay updates, and trigger self-healing workflows on failures to reduce manual recovery effort.

What is self-healing CI and how does it handle pipeline failures across branches?

Self-healing CI automatically orchestrates fixes for failed pipeline attempts across branches using configurable timeouts, subagent polling, and stateful coordination to safely recover CI health.

Can I configure timeout limits and cycle limits for automated CI recovery workflows?

Configurable timeouts and user cycle limits balance automation control. Overrides are supported for retries, no-new-ci-attempts, environment reruns, and self-healing workflows.

How do I start monitoring CI health for my current git branch?

Start monitoring CI health for the current git branch by running the monitor-ci command, which initiates background Nx Cloud pipeline status polling and failure alerting.

Does CI monitoring support handling retries for environment reruns and no-new-ci-attempts?

CI monitoring handles retries for no-new-ci-attempts and environment reruns by enforcing safety patterns and robust status handling to maintain recoverable pipeline health.

What are the limitations of using automated self-healing workflows for CI monitoring?

Automated self-healing workflows require careful orchestration of subagents and MCP interactions. Limitations include managing cycle limits and preventing unsafe recoveries during stateful coordination.