monitor-ci

Monitors Nx Cloud CI pipelines and applies automated self-healing fixes.

1|Updated Jun 12, 2024
One-click install
npx skills add https://github.com/cskiwi/badman-m3 --skill monitor-ci-cskiwi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitor-ci
Source: https://github.com/cskiwi/badman-m3/tree/main/.claude/skills/monitor-ci
Command: npx skills add https://github.com/cskiwi/badman-m3 --skill monitor-ci-cskiwi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @nx/cloud, ci-poll-decide.mjs, ci-state-update.mjs, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the monitoring of your Nx Cloud CI pipeline, proactively identifying failures and attempting self-healing fixes to keep your development workflow smooth and efficient.

Core Features & Use Cases

  • CI Pipeline Monitoring: Continuously tracks the status of Nx Cloud CI attempts for your branches.
  • Automated Self-Healing: Detects common CI failures (e.g., lockfile issues) and attempts to fix them automatically.
  • Intelligent Decision Making: Uses deterministic scripts to analyze CI results and decide on the best course of action, from retrying tasks to applying verified fixes.
  • Use Case: When a CI pipeline fails on a pull request, this Skill can automatically detect the failure, identify a potential cause like a stale lockfile, update it, and re-run the CI, all without manual intervention.

Quick Start

Use the monitor-ci skill to watch the CI pipeline for the current branch and attempt to fix any detected issues.

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 failure resolution?

Automate Nx Cloud CI pipeline monitoring by tracking branch CI attempts, detecting failures, and applying automated self-healing fixes like updating stale lockfiles without manual intervention.

Can I automatically fix lockfile issues when a Nx Cloud CI pipeline fails?

Yes, automated self-healing detects common CI failures such as stale lockfile issues, automatically updates the lockfile, and re-runs the CI pipeline to resolve the failure.

How does automated CI self-healing decide whether to retry tasks or apply fixes?

Automated CI self-healing uses deterministic scripts to analyze CI results and decide the best course of action, from retrying tasks to applying verified local fixes or resolving environment issues.

Do I need Nx Cloud to use automated CI monitoring and self-healing scripts?

Yes, this CI monitoring integrates with Nx Cloud's MCP tools for deterministic decision-making and state management, requiring the Nx Cloud environment to manage CI attempt lifecycles effectively.

What types of CI failures can automated pipeline monitoring resolve?

Automated pipeline monitoring resolves common CI failures including lockfile issues, environment problems, and task errors by applying verified local fixes and managing CI attempt lifecycles.

When should I avoid using automated self-healing for CI pipelines?

Avoid automated self-healing when CI failures require complex, non-deterministic code changes, as the system relies on deterministic scripts to apply verified fixes and manage CI attempt lifecycles.