nomcopter/react-mosaic/monitor-ci

Monitor CI Command

You are the orchestrator for monitoring Nx Cloud CI pipeline executions and handling self-healing fixes. You spawn the ci-monitor-subagent subagent to poll CI status and make decisions based on the results.

Context

• Current Branch: !git branch --show-current
• Current Commit: !git rev-parse --short HEAD
• Remote Status: !git status -sb | head -1

User Instructions

$ARGUMENTS

Important: If user provides specific instructions, respect them over default behaviors described below.

Configuration Defaults

Parse any overrides from $ARGUMENTS and merge with defaults.

Nx Cloud Connection Check

CRITICAL: Before starting the monitoring loop, verify the workspace is connected to Nx Cloud.

Step 0: Verify Nx Cloud Connection

1. Check `nx.json` at workspace root for nxCloudId or nxCloudAccessToken
2. If `nx.json` missing OR neither property exists → exit with:

`` [monitor-ci] Nx Cloud not connected. Unlock 70% faster CI and auto-fix broken PRs with https://nx.dev/nx-cloud ``

1. If connected → continue to main loop

Anti-Patterns (NEVER DO)

CRITICAL: The following behaviors are strictly prohibited:

If this skill fails to activate, the fallback is:

1. Use CI provider CLI for READ-ONLY status check (single call, no watch/polling flags)
2. Immediately delegate to this skill with gathered context
3. NEVER continue polling on main agent

CI provider CLIs are acceptable ONLY for:

• One-time read of PR/pipeline status
• Getting PR/branch metadata
• NOT for continuous monitoring or watch mode

Session Context Behavior

Important: Within a Claude Code session, conversation context persists. If you Ctrl+C to interrupt the monitor and re-run /monitor-ci, Claude remembers the previous state and may continue from where it left off.

• To continue monitoring: Just re-run /monitor-ci (context is preserved)
• To start fresh: Use /monitor-ci --fresh to ignore previous context
• For a completely clean slate: Exit Claude Code and restart claude

Default Behaviors by Status

The subagent returns with one of the following statuses. This table defines the default behavior for each status. User instructions can override any of these.

Fix Available Decision Logic

When subagent returns fix_available, main agent compares failedTaskIds vs verifiedTaskIds:

Step 1: Categorize Tasks

1. Verified tasks = tasks in both failedTaskIds AND verifiedTaskIds
2. Unverified tasks = tasks in failedTaskIds but NOT in verifiedTaskIds
3. E2E tasks = unverified tasks where target contains "e2e" (task format: <project>:<target> or <project>:<target>:<config>)
4. Verifiable tasks = unverified tasks that are NOT e2e

Step 2: Determine Path

Step 3a: Apply via MCP (fully/e2e-only verified)

• Call update_self_healing_fix({ shortLink, action: "APPLY" })
• Record last_cipe_url, spawn subagent in wait mode

Step 3b: Local Verification Flow

When verifiable (non-e2e) unverified tasks exist:

1. Detect package manager:

• pnpm-lock.yaml exists → pnpm nx
• yarn.lock exists → yarn nx
• Otherwise → npx nx

1. Run verifiable tasks in parallel:

• Spawn general subagents to run each task concurrently
• Each subagent runs: <pm> nx run <taskId>
• Collect pass/fail results from all subagents

1. Evaluate results:

1. Apply-locally + enhance flow:

• Run nx-cloud apply-locally <shortLink>
• Enhance the code to fix failing tasks
• Run failing tasks again to verify fix
• If still failing → increment local_verify_count, loop back to enhance
• If passing → commit and push, record expected_commit_sha, spawn subagent in wait mode

1. Track attempts (wraps step 4):

• Increment local_verify_count after each enhance cycle
• If local_verify_count >= local_verify_attempts (default: 3):

• Get code in commit-able state
• Commit and push with message indicating local verification failed
• Report to user:

`` [monitor-ci] Local verification failed after <N> attempts. Pushed to CI for final validation. Failed: <taskIds> ``

• Record expected_commit_sha, spawn subagent in wait mode (let CI be final judge)

Commit Message Format

git commit -m "fix(<projects>): <brief description>
 
Failed tasks: <taskId1>, <taskId2>
Local verification: passed|enhanced|failed-pushing-to-ci"

Git Safety: Only stage and commit files that were modified as part of the fix. Users may have concurrent local changes (local publish, WIP features, config tweaks) that must NOT be committed. NEVER use git add -A or git add . — always stage specific files by name.

Unverified Fix Flow (No Verification Attempted)

When verificationStatus is FAILED, NOT_EXECUTABLE, or fix has couldAutoApplyTasks != true with no verification:

• Analyze fix content (suggestedFix, suggestedFixReasoning, taskOutputSummary)
• If fix looks correct → apply via MCP
• If fix needs enhancement → use Apply Locally + Enhance Flow above
• If fix is wrong → reject via MCP, fix from scratch, commit, push

Auto-Apply Eligibility

The couldAutoApplyTasks field indicates whether the fix is eligible for automatic application:

• `true`: Fix is eligible for auto-apply. Subagent keeps polling while verification is in progress. Returns fix_auto_applying when verified, or fix_available if verification fails.
• `false` or `null`: Fix requires manual action (apply via MCP, apply locally, or reject)