home / skills / constellos / claude-code / ci-orchestration

This skill helps you monitor CI status, extract preview URLs, and manage retries with fail-fast patterns for efficient CI/CD orchestration.

npx playbooks add skill constellos/claude-code --skill ci-orchestration

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
3.5 KB
---
name: CI Orchestration
description: Use this skill when the user wants to "check CI", "wait for CI", "CI status", "retry failed checks", "cancel CI", "debug CI failure", or manage CI/CD workflows. Provides comprehensive CI checking with fail-fast patterns and preview URL extraction.
version: 0.1.0
---

# CI Orchestration

Comprehensive CI/CD workflow management with fail-fast error detection and preview URL extraction.

## Purpose

CI Orchestration provides explicit control over GitHub Actions and other CI systems. Monitor check status, extract preview URLs, debug failures, and manage workflow retries with intelligent fail-fast patterns.

## When to Use

- Waiting for CI checks with real-time status
- Extracting preview deployment URLs (Vercel, Netlify)
- Debugging CI failures
- Retrying failed workflows
- Managing CI in complex workflows

## Core Capabilities

### Check CI Status

```bash
# Check PR status
gh pr checks 42

# Watch and wait
gh pr checks 42 --watch

# Get JSON output
gh pr view 42 --json statusCheckRollup
```

### Extract Preview URLs

The existing `ci-status.ts` utility provides comprehensive preview URL extraction:

```typescript
import { extractPreviewUrls } from '../shared/hooks/utils/ci-status.js';

// Extract from CI output
const urls = extractPreviewUrls(ciOutput);
// Returns: { web: 'https://...', marketing: 'https://...' }
```

### Fail-Fast Patterns

```bash
# Wait with fail-fast
awaitCIWithFailFast "$PWD" 42 10  # 10 minute timeout

# Detects:
# - Merge conflicts
# - Branch divergence
# - Failed checks
# - Workflow errors
```

### Retry Failed Checks

```bash
# Get latest workflow run
RUN_ID=$(gh run list --branch $(git branch --show-current) --limit 1 --json databaseId -q '.[0].databaseId')

# Re-run failed jobs
gh run rerun $RUN_ID --failed
```

## Integration with Hooks

| Hook | Behavior |
|------|----------|
| await-pr-status | Waits for CI after `gh pr create` |
| commit-task-await-ci-status | Auto-commits and checks CI on SubagentStop |
| commit-session-await-ci-status | Blocking CI check on Stop |

## Utilities

From `ci-status.ts`:
- `awaitCIWithFailFast(cwd, prNumber, timeout)` - Wait with fail-fast
- `extractPreviewUrls(output)` - Parse Vercel/Netlify URLs
- `getLatestCIRun(cwd, branch)` - Get workflow run ID
- `formatCiChecksTable(checks)` - Format as markdown table

## Examples

### Wait for CI with Preview URLs

```bash
# Create PR
PR=$(gh pr create --title "Add feature" --body "..." --json number -q .number)

# Wait for CI
awaitCIWithFailFast "$PWD" $PR 10

# Extract preview URLs
CHECKS=$(gh pr view $PR --json statusCheckRollup -q '.statusCheckRollup')
PREVIEW=$(extractPreviewUrls "$CHECKS")

echo "Preview: $PREVIEW"
```

### Debug Failed CI

```bash
# Get failed checks
gh pr checks 42 --json name,conclusion,detailsUrl \
  --jq '.[] | select(.conclusion=="FAILURE") | {name, url: .detailsUrl}'

# View logs
gh run view $(gh run list --limit 1 --json databaseId -q '.[0].databaseId') --log-failed
```

### Retry with Backoff

```bash
MAX_RETRIES=3
RETRY=0

while [ $RETRY -lt $MAX_RETRIES ]; do
  if gh pr checks $PR --watch; then
    echo "✓ CI passed"
    break
  fi

  RETRY=$((RETRY + 1))
  if [ $RETRY -lt $MAX_RETRIES ]; then
    echo "Retry $RETRY/$MAX_RETRIES..."
    gh run rerun $(gh run list --limit 1 --json databaseId -q '.[0].databaseId') --failed
  fi
done
```

## Best Practices

1. Use fail-fast patterns (10min timeout)
2. Extract and share preview URLs
3. Auto-retry transient failures (max 3 times)
4. Parse logs for actionable errors
5. Update PR comments with CI status

Overview

This skill provides CI orchestration for GitHub Actions and other CI systems, enabling monitoring, fail-fast waiting, retrying, and preview URL extraction. It helps surface actionable failures, extract deployment previews, and automate common CI management tasks for pull requests and branches.

How this skill works

The skill inspects CI run status, checks rollups, and workflow run metadata to determine pass/fail state and detect merge conflicts or branch divergence. It can wait for checks with fail-fast timeouts, parse CI output to extract Vercel/Netlify preview URLs, and trigger reruns for failed jobs. It also formats CI check summaries and links to failed-job logs for debugging.

When to use it

  • Waiting for PR CI checks to complete before merging
  • Extracting preview or staging URLs from CI output to share with reviewers
  • Retrying flaky jobs or re-running only failed checks
  • Debugging CI failure by collecting failed-job URLs and logs
  • Blocking or gating workflow steps on CI success

Best practices

  • Use a short fail-fast timeout (e.g., 10 minutes) to surface early, actionable failures
  • Limit automatic retries to transient errors (max ~3 attempts) with backoff
  • Always extract and share preview URLs for QA and reviewers
  • Parse failed-job logs to find root causes before rerunning
  • Update PR comments with CI status and links to debug artifacts

Example use cases

  • Wait for CI on a newly created PR, then extract and echo preview URLs for reviewers
  • Watch CI with fail-fast logic to detect merge conflicts or branch divergence early
  • Collect failed checks and open their logs to debug failing tests or build steps
  • Automatically rerun only failed jobs for a flaky test suite with a retry loop
  • Format CI checks into a compact table and post it to a PR comment for maintainers

FAQ

How does fail-fast behavior work?

Fail-fast watches checks and triggers an early exit when a blocking condition is detected (merge conflict, branch divergence, or failing workflow), using a configured timeout to avoid long waits.

What preview URLs can it extract?

It parses CI output for common deployment providers (examples: Vercel, Netlify) and returns categorized web or marketing preview URLs to share with reviewers.