monitor-ci

Monitor Nx Cloud CI pipelines and apply self-healing fixes automatically.

11|5|Updated Jun 30, 2019
One-click install
npx skills add https://github.com/ikemtz/AngularMonoRepo --skill monitor-ci-ikemtz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitor-ci
Source: https://github.com/ikemtz/AngularMonoRepo/tree/main/src/.opencode/skills/monitor-ci
Command: npx skills add https://github.com/ikemtz/AngularMonoRepo --skill monitor-ci-ikemtz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monitors Nx Cloud CI pipelines and coordinates self-healing fixes to minimize manual intervention and CI downtime.

Core Features & Use Cases

  • Spawns the ci-monitor-subagent to poll CI status and relay updates to users.
  • Automatically handles self-healing workflows including applying fixes via MCP or locally, and supports wait-mode for new CI attempts.
  • Works within Nx workspaces to monitor branch-specific CI runs and respond to statuses like IN_PROGRESS, FAILED, or SUCCEEDED; ideal for teams relying on Nx Cloud automation and pre/post-CI workflows.

Quick Start

Start monitoring the current branch's Nx Cloud CI and handle self-healing fixes automatically.

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?

To automate Nx Cloud CI pipeline monitoring and self-healing, use a dedicated subagent that polls branch-specific run statuses and automatically applies fixes when pipelines fail, minimizing manual intervention.

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

Self-healing CI automatically applies fixes when a pipeline fails. Within Nx workspaces, a subagent polls Nx Cloud run statuses like FAILED and triggers auditable auto-fix workflows locally or via MCP without extra tooling.

Do I need an active Nx Cloud connection to monitor branch-based CI runs?

Yes, monitoring branch-based CI runs requires an active Nx Cloud connection. The subagent polls Nx Cloud pipeline statuses, such as IN_PROGRESS or SUCCEEDED, and synchronizes wait-mode CI attempts based on that connection.

Can I automatically retry failed Nx Cloud CI attempts without extra tooling?

Yes, you can automatically handle failed Nx Cloud CI attempts without extra tooling. The system supports wait-mode for new CI attempts and applies self-healing fixes via MCP or locally, controlled by defaults like max-cycles and timeout.

What are the limitations of automating CI fixes with a subagent?

Automating CI fixes with a subagent is limited by configured max-cycles and timeout defaults. It honors safe, auditable actions and requires an active Nx Cloud connection, meaning it cannot operate offline or bypass Nx Cloud pipeline status tracking.

When should I use auto-fix workflows for Nx Cloud CI pipelines?

You should use auto-fix workflows for Nx Cloud CI pipelines when you need to minimize CI downtime across Nx workspaces. This approach is ideal for teams relying on Nx Cloud automation to handle pre/post-CI workflows and branch-specific failures.