monitor-ci

Monitor Nx Cloud CI Attempts and apply self-healing fixes.

3|1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/wahidyankf/ose-primer --skill monitor-ci-wahidyankf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: monitor-ci
Source: https://github.com/wahidyankf/ose-primer/tree/main/.opencode/skills/monitor-ci
Command: npx skills add https://github.com/wahidyankf/ose-primer --skill monitor-ci-wahidyankf

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Manually tracking Nx Cloud CI pipeline status and resolving failures is time-consuming, and native CI provider tools like gh or glab cannot access Nx Cloud's self-healing capabilities, leaving developers to fix issues manually without automated support.

Core Features & Use Cases

  • Automated CI Polling: Continuously monitors Nx Cloud CI Attempts for your branch without manual checks or context-heavy polling on the main agent.
  • Self-Healing Integration: Leverages Nx Cloud's automated fix generation to resolve common CI failures like lint errors or flaky tests without developer intervention.
  • Local Verification & Fixes: Handles unverified fixes by running local tests, manages environment reruns for infrastructure-related failures, and enforces git safety to avoid committing unrelated work.
  • Use Case: If a PR's CI fails due to a minor code issue or flaky test, the skill can automatically apply a verified fix or guide you through local verification, cutting down resolution time from minutes to seconds.

Quick Start

Use the monitor-ci skill to track the CI status for your current branch and automatically handle any self-healing fixes that are generated.

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 self-healing fixes?

Automate Nx Cloud CI monitoring by continuously polling CI Attempt status for your branch and applying verified automated fixes generated by Nx Cloud's self-healing API to resolve failures without manual intervention. This reduces mean time to resolve CI failures significantly.

Can I apply Nx Cloud self-healing fixes using standard gh or glab commands?

No, native CI provider tools like gh or glab cannot access Nx Cloud's self-healing capabilities. You need a specialized approach to leverage automated fix generation for common CI failures like lint errors or flaky tests directly within your Nx monorepo workflow.

What is the process for handling unverified CI fixes in an Nx monorepo?

Handling unverified CI fixes involves running local tests to verify the fix, managing environment reruns for infrastructure failures, and enforcing git safety to avoid committing unrelated work during the self-healing process for your Nx monorepo.

Does this approach work with budget-gated local fix attempts for CI pipelines?

Yes, the approach satisfies requirements for budget-gated local fix attempts by integrating CI state tracking with Nx Cloud's self-healing API to manage fix verification and apply changes only when safe and verified, cutting down resolution time.

When do I need automated polling for Nx CI pipeline executions?

You need automated polling for Nx CI pipeline executions when manual tracking becomes time-consuming and you want to automatically track CI Attempt status, apply generated fixes, and resolve environment or code failures without context-heavy polling on your main agent.