monitor-ci

Monitor Nx Cloud CI pipelines by running deterministic polling scripts that track pipeline failures, evaluate gate checks, and coordinate MCP tool calls to apply, reject, or rerun automated fixes. The skill orchestrates self-healing cycles and manages commits.

CI self-healing orchestration in an Nx Cloud monorepo coordinates MCP tool calls to gather failure details, gate local verifications, manage commits, and trigger new CI attempts without manual intervention. It tracks cycles and gates via deterministic state updates.

Automate retries for failed Nx Cloud CI attempts by configuring deterministic decision scripts that evaluate wait-mode settings, apply or enhance fixes via MCP tool calls, and trigger new CI attempts. The skill tracks cycles and respects gate checks.

Yes, you can use MCP tool calls to apply, reject, rerun, or enhance automated fixes on Nx Cloud CI branches. The skill coordinates these tool calls with deterministic state updates to manage self-healing cycles and gate checks.

Limitations of automated CI self-healing include dependency on Nx Cloud connectivity as the source of truth, potential stuck repair loops if gate checks fail, and the need for deterministic decision scripting to prevent endless polling cycles.

Yes, Nx Cloud connectivity is required because the skill uses Nx Cloud as the source of truth for CI status. It ensures deterministic decision scripting and MCP tool calls coordinate with configurable cycles and gate checks during polling.