monitor-ci

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

Updated Feb 12, 2026
One-click install
npx skills add https://github.com/Clogogo/audit_app --skill monitor-ci-clogogo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitor-ci
Source: https://github.com/Clogogo/audit_app/tree/main/.github/skills/monitor-ci
Command: npx skills add https://github.com/Clogogo/audit_app --skill monitor-ci-clogogo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monitor Nx Cloud CI pipelines and handle self-healing fixes to reduce manual monitoring and accelerate CI outcomes.

Core Features & Use Cases

  • Continuous CI monitoring across branches and environments
  • Self-healing fix generation via a dedicated subagent
  • Flexible workflow controls including MCP-based apply or local patching
  • Handling no-new-cipe and environment rerun scenarios
  • Clear guidance and user prompts for cycle limits and overrides

Quick Start

Start by running the monitor-ci command to begin automated CI health checks and self-healing on your 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 Nx Cloud CI monitoring and fix failing pipelines automatically?

To automate Nx Cloud CI monitoring, use a tool that continuously checks pipelines across branches and triggers self-healing fixes when failures occur. It handles timeouts, retries, and waits for new CI attempts to keep pipelines green.

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

Self-healing CI is an automated workflow orchestration process that detects pipeline failures and generates fixes without manual intervention. It operates across branches, handles timeouts and retries, and applies patches locally or via MCP.

Do I need an existing Nx workspace to start monitoring CI pipelines?

Yes, an existing Nx workspace with Nx Cloud configured is required to start monitoring CI pipelines. Optional override settings can be parsed from user arguments to customize the self-healing workflow controls.

Can I apply CI self-healing fixes locally instead of using MCP?

Yes, you can apply CI self-healing fixes locally instead of using MCP. The workflow orchestration controls offer flexible patching options, allowing you to choose between MCP-based apply or local patching to resolve failures.

How does CI monitoring handle no-new-CI attempts or environment reruns?

CI monitoring handles no-new-CI attempts and environment rerun scenarios by waiting for new CI attempts and applying generated fixes. It provides clear user prompts for cycle limits and overrides during these edge cases.