monitor-ci

1. Check nx.json at workspace root for nxCloudId or nxCloudAccessToken

2. If nx.json missing OR neither property exists → exit with:

   Copy

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

3. If connected → continue to main loop

Repeat until done:

Determine select fields based on mode:

• Wait mode: use WAIT_FIELDS (cipeUrl,commitSha,cipeStatus)
• Normal mode (first poll or after newCipeDetected): use LIGHT_FIELDS {%- if platform == "claude" %}

{% raw %}

Task(
  agent: "ci-monitor-subagent",
  model: haiku,
  prompt: "FETCH_STATUS for branch '<branch>'.
           select: '<fields>'"
)

{% endraw %}

The subagent calls ci_information and returns a JSON object with the requested fields. This is a foreground call — wait for the result. {%- else %}

Call the ci_information tool with the determined select fields for the current branch. Wait for the result before proceeding. {%- endif %}

node <skill_dir>/scripts/ci-poll-decide.mjs '<subagent_result_json>' <poll_count> <verbosity> \
  [--wait-mode] \
  [--prev-cipe-url <last_cipe_url>] \
  [--expected-sha <expected_commit_sha>] \
  [--prev-status <prev_status>] \
  [--timeout <timeout_minutes>] \
  [--new-cipe-timeout <new_cipe_timeout_minutes>] \
  [--elapsed-seconds <seconds_since_start_time>] \
  [--env-rerun-count <env_rerun_count>] \
  [--no-progress-count <no_progress_count>] \
  [--prev-cipe-status <prev_cipe_status>] \
  [--prev-sh-status <prev_sh_status>] \
  [--prev-verification-status <prev_verification_status>] \
  [--prev-failure-classification <prev_failure_classification>]

Pass --timeout and --new-cipe-timeout in minutes (the values from Configuration Defaults) — the script converts to seconds internally. Pass --elapsed-seconds as the whole seconds elapsed since start_time (now() - start_time); this is what enforces --timeout as a total monitor budget across every poll and attempt, so it must be supplied on every call once monitoring has started.

The script outputs a single JSON line: { action, code, message, delay?, noProgressCount, envRerunCount, fields?, newCipeDetected?, verifiableTaskIds? }

Parse the JSON output and update tracking state:

• no_progress_count = output.noProgressCount
• env_rerun_count = output.envRerunCount
• prev_cipe_status = subagent_result.cipeStatus
• prev_sh_status = subagent_result.selfHealingStatus
• prev_verification_status = subagent_result.verificationStatus
• prev_failure_classification = subagent_result.failureClassification
• prev_status = output.action + ":" + (output.code || subagent_result.cipeStatus)
• poll_count++

Based on action:

• action == "poll": Print output.message, sleep output.delay seconds, go to 2a
  • If output.newCipeDetected: clear wait mode, reset wait_mode = false
• action == "wait": Print output.message, sleep output.delay seconds, go to 2a
• action == "done": Proceed to Step 3 with output.code

When decision script returns action == "done":

1. Run cycle-check (Step 4) before handling the code
2. Check the returned code
3. Look up default behavior in the table above
4. Check if user instructions override the default
5. Execute the appropriate action
6. If action expects new CI Attempt, update tracking (see Step 3a)
7. If action results in looping, go to Step 2 {%- if platform == "claude" %}

Several statuses require fetching heavy data or calling MCP:

• fix_apply_ready: Spawn UPDATE_FIX subagent with APPLY
• fix_needs_local_verify: Spawn FETCH_HEAVY subagent for fix details before local verification
• fix_needs_review: Spawn FETCH_HEAVY subagent → get suggestedFixDescription, suggestedFixSummary, taskFailureSummaries
• fix_failed / no_fix: Spawn FETCH_HEAVY subagent → get taskFailureSummaries for local fix context
• environment_issue: Spawn UPDATE_FIX subagent with RERUN_ENVIRONMENT_STATE
• self_healing_throttled: Spawn FETCH_HEAVY subagent → get selfHealingSkipMessage; then FETCH_THROTTLE_INFO + UPDATE_FIX for each old fix {%- else %}

Several statuses require fetching additional data or calling tools:

• fix_apply_ready: Call update_self_healing_fix with action APPLY
• fix_needs_local_verify: Call ci_information with HEAVY_FIELDS for fix details before local verification
• fix_needs_review: Call ci_information with HEAVY_FIELDS → get suggestedFixDescription, suggestedFixSummary, taskFailureSummaries
• fix_failed / no_fix: Call ci_information with HEAVY_FIELDS → get taskFailureSummaries for local fix context
• environment_issue: Call update_self_healing_fix with action RERUN_ENVIRONMENT_STATE
• self_healing_throttled: Call ci_information with HEAVY_FIELDS → get selfHealingSkipMessage; then call update_self_healing_fix for each old fix {%- endif %}

After actions that should trigger a new CI Attempt, run:

node <skill_dir>/scripts/ci-state-update.mjs post-action \
  --action <type> \
  --cipe-url <current_cipe_url> \
  --commit-sha <git_rev_parse_HEAD>

Action types: fix-auto-applying, apply-mcp, apply-local-push, reject-fix-push, local-fix-push, env-rerun, auto-fix-push, empty-commit-push

The script returns { waitMode, pollCount, lastCipeUrl, expectedCommitSha, agentTriggered }. Update all tracking state from the output, then go to Step 2.

When the decision script returns action == "done", run cycle-check before handling the code:

node <skill_dir>/scripts/ci-state-update.mjs cycle-check \
  --code <code> \
  [--agent-triggered] \
  --cycle-count <cycle_count> --max-cycles <max_cycles> \
  --env-rerun-count <env_rerun_count>

The script returns { cycleCount, agentTriggered, envRerunCount, approachingLimit, limitReached, message }. Update tracking state from the output.

• If limitReached → the --max-cycles budget is exhausted. Print message and stop monitoring (do not handle the code or start another cycle). This is a hard stop, not advisory.
• Else if approachingLimit → ask user whether to continue (with 5 or 10 more cycles) or stop monitoring
• If previous cycle was NOT agent-triggered (human pushed), log that human-initiated push was detected

• no_progress_count, circuit breaker (5 polls), and backoff reset are handled by ci-poll-decide.mjs (progress = any change in cipeStatus, selfHealingStatus, verificationStatus, or failureClassification)
• env_rerun_count reset on non-environment status is handled by ci-state-update.mjs cycle-check
• On new CI Attempt detected (poll script returns newCipeDetected) → reset local_verify_count = 0, env_rerun_count = 0