Claude Skill

ci

Monitor the CI pipeline for the current branch via a background Monitor script (GitHub or GitLab), reacting to pass, fail, and manual-gate states. Use when the user says 'watch CI', 'monitor the pipeline', 'is CI green', or after pushing a branch or creating a PR/MR.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download domengabrovsek-agent-config-skills_ci-7bb2849.zip · 4 KB

Install

skills CLI npx skills add https://github.com/domengabrovsek/agent-config/tree/main/skills/ci
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install domengabrovsek-claude@llmmart
Git git clone https://github.com/domengabrovsek/agent-config.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole domengabrovsek/claude collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Monitor CI Pipeline

Workflow

why-no-hook: skill workflow guidance; each step requires understanding the surrounding context (repo, task shape, prior state).

  1. Detect VCS platform: .gitlab-ci.yml -> glab, .github/ -> gh (review-time: see section note)
  2. Start a Monitor with the matching script: (review-time: see section note)
    • GitHub: bash scripts/gh-ci-monitor.sh, resolved inside this skill's own directory (review-time: see section note)
    • GitLab: bash scripts/glab-ci-monitor.sh, resolved inside this skill's own directory (review-time: see section note)
    • Use timeout_ms: 1800000, the Monitor maximum of 30 minutes (review-time: see section note)
    • Description: "CI pipeline on
  3. React to Monitor notifications: (review-time: see section note)
    • Monitor expiry before a completed|* status: re-arm the same script, since CI pipelines can outlast 30 minutes. The restarted script re-emits the current status (review-time: see section note)
    • no-runs|<branch>: no CI runs found for this branch - inform the user and stop (review-time: see section note)
    • error|persistent-failure: the monitor script hit 5 consecutive errors - report and stop (review-time: see section note)
    • Status change (e.g., in_progress|null → completed|success): acknowledge briefly (review-time: see section note)
    • Pipeline passes (completed|success): (review-time: see section note)
      • Run ~/.agents/scripts/notify.sh "CI passed - <branch-name>" (review-time: see section note)
      • Report success (review-time: see section note)
    • Pipeline awaiting manual action (completed|manual, GitLab only): (review-time: see section note)
      • All automatic jobs completed; the pipeline is paused on a manual gate and will not progress without user action (review-time: see section note)
      • Run ~/.agents/scripts/notify.sh "CI awaiting manual action - <branch-name>" (review-time: see section note)
      • Report status and stop watching - do NOT trigger the manual job automatically (review-time: see section note)
    • Pipeline fails (completed|failure or any non-success conclusion): (review-time: see section note)
      1. Fetch the job log:
        • GitLab: glab ci trace <job-id> (review-time: see section note)
        • GitHub: gh run view <run-id> --log-failed (review-time: see section note)
      2. Do NOT pipe output through head, tail, grep, or any other command - run the commands directly
      3. Analyze the root cause - identify the specific failure (test, lint, type check, build, coverage, etc.)
      4. Classify the failure as transient or real before proposing any change - transient = infra outage, rate limit, queued/timed-out runner, auth/network flake, registry or dependency propagation delay; real = a test/lint/type/build/coverage failure caused by the code under change. State the classification (review-time: see section note)
      5. If transient: re-run the failed job (gh run rerun <run-id> --failed / glab ci retry <job-id>) and keep monitoring - do NOT edit code for a transient failure. Escalate to the user only if it recurs after a re-run (review-time: see section note)
      6. Run ~/.agents/scripts/notify.sh "CI failed - <failure-summary>"
      7. If real, fix it: make the change, run npm run verify:fast when package.json declares it, otherwise /verify-done. Commit, push, and keep monitoring. The push hook runs the fast gate again (review-time: see section note)
      8. Before gh pr ready: with a declared verify, the hook needs <git-dir>/verify-passed equal to HEAD. Run npm run verify once if it is not (review-time: see section note)
      9. Report what failed and what changed in the same message as the next action (review-time: see section note)

How it works

The monitor scripts poll CI status every 30 seconds but only emit a line when the status changes. This means:

  • Zero token cost while the pipeline is running and status hasn't changed (review-time: see section note)
  • Claude reacts within ~30s of a status change (vs up to 2 min with /loop) (review-time: see section note)
  • No CronDelete cleanup needed - the script exits on terminal state, ending the Monitor (review-time: see section note)
  • If gh/glab fails 5 times in a row (auth expired, network down), the script exits with an error notification (review-time: see section note)

Important: Non-interactive commands only

These commands require a TTY and will NOT work - never use them:

  • glab ci view (interactive TUI) (review-time: see section note)
  • gh run watch (interactive watcher) (review-time: see section note)
  • Any command with --web flag (opens browser) (review-time: see section note)

Safe commands to use:

  • glab ci status, glab ci list, glab ci trace <job-id> (review-time: see section note)
  • gh pr checks, gh run list, gh run view <run-id> --log-failed (review-time: see section note)

Guardrails

  • After 3 consecutive failures on the same issue, stop and escalate - something structural is wrong (review-time: see section note)
  • Never weaken tests, skip linting, or lower coverage thresholds to make CI pass (review-time: see section note)
  • Never use --no-verify or skip hooks (review-time: see section note)
  • A failure unrelated to your changes (flaky test, infra issue) is transient: re-run it per step e, and do not edit code for it (review-time: see section note)
Files (claude)
  • scripts
    • gh-ci-monitor.sh 2.5 KB
      Loading…
    • glab-ci-monitor.sh 1.7 KB
      Loading…
  • SKILL.md 5.8 KB
    ---
    name: ci
    description: "Monitor the CI pipeline for the current branch via a background Monitor script (GitHub or GitLab), reacting to pass, fail, and manual-gate states. Use when the user says 'watch CI', 'monitor the pipeline', 'is CI green', or after pushing a branch or creating a PR/MR."
    ---
    
    # Monitor CI Pipeline
    
    ## Workflow
    
    **why-no-hook:** skill workflow guidance; each step requires understanding the surrounding context (repo, task shape, prior state).
    
    1. **Detect VCS platform**: `.gitlab-ci.yml` -> glab, `.github/` -> gh `(review-time: see section note)`
    2. **Start a Monitor** with the matching script: `(review-time: see section note)`
       - GitHub: `bash scripts/gh-ci-monitor.sh`, resolved inside this skill's own directory `(review-time: see section note)`
       - GitLab: `bash scripts/glab-ci-monitor.sh`, resolved inside this skill's own directory `(review-time: see section note)`
       - Use `timeout_ms: 1800000`, the Monitor maximum of 30 minutes `(review-time: see section note)`
       - Description: "CI pipeline on <branch-name>" `(review-time: see section note)`
    3. **React to Monitor notifications**: `(review-time: see section note)`
       - Monitor expiry before a `completed|*` status: re-arm the same script, since CI pipelines can outlast 30 minutes. The restarted script re-emits the current status `(review-time: see section note)`
       - `no-runs|<branch>`: no CI runs found for this branch - inform the user and stop `(review-time: see section note)`
       - `error|persistent-failure`: the monitor script hit 5 consecutive errors - report and stop `(review-time: see section note)`
       - Status change (e.g., `in_progress|null` → `completed|success`): acknowledge briefly `(review-time: see section note)`
       - **Pipeline passes** (`completed|success`): `(review-time: see section note)`
         - Run `~/.agents/scripts/notify.sh "CI passed - <branch-name>"` `(review-time: see section note)`
         - Report success `(review-time: see section note)`
       - **Pipeline awaiting manual action** (`completed|manual`, GitLab only): `(review-time: see section note)`
         - All automatic jobs completed; the pipeline is paused on a manual gate and will not progress without user action `(review-time: see section note)`
         - Run `~/.agents/scripts/notify.sh "CI awaiting manual action - <branch-name>"` `(review-time: see section note)`
         - Report status and stop watching - do NOT trigger the manual job automatically `(review-time: see section note)`
       - **Pipeline fails** (`completed|failure` or any non-success conclusion): `(review-time: see section note)`
         a. Fetch the job log:
            - GitLab: `glab ci trace <job-id>` `(review-time: see section note)`
            - GitHub: `gh run view <run-id> --log-failed` `(review-time: see section note)`
         b. Do NOT pipe output through head, tail, grep, or any other command - run the commands directly
         c. Analyze the root cause - identify the specific failure (test, lint, type check, build, coverage, etc.)
         d. **Classify the failure as transient or real before proposing any change** - transient = infra outage, rate limit, queued/timed-out runner, auth/network flake, registry or dependency propagation delay; real = a test/lint/type/build/coverage failure caused by the code under change. State the classification `(review-time: see section note)`
         e. **If transient**: re-run the failed job (`gh run rerun <run-id> --failed` / `glab ci retry <job-id>`) and keep monitoring - do NOT edit code for a transient failure. Escalate to the user only if it recurs after a re-run `(review-time: see section note)`
         f. Run `~/.agents/scripts/notify.sh "CI failed - <failure-summary>"`
         g. **If real, fix it**: make the change, run `npm run verify:fast` when package.json declares it, otherwise `/verify-done`. Commit, push, and keep monitoring. The push hook runs the fast gate again `(review-time: see section note)`
         h. **Before `gh pr ready`**: with a declared `verify`, the hook needs `<git-dir>/verify-passed` equal to HEAD. Run `npm run verify` once if it is not `(review-time: see section note)`
         i. Report what failed and what changed in the same message as the next action `(review-time: see section note)`
    
    ## How it works
    
    The monitor scripts poll CI status every 30 seconds but only emit a line when the status **changes**. This means:
    
    - Zero token cost while the pipeline is running and status hasn't changed `(review-time: see section note)`
    - Claude reacts within ~30s of a status change (vs up to 2 min with /loop) `(review-time: see section note)`
    - No CronDelete cleanup needed - the script exits on terminal state, ending the Monitor `(review-time: see section note)`
    - If `gh`/`glab` fails 5 times in a row (auth expired, network down), the script exits with an error notification `(review-time: see section note)`
    
    ## Important: Non-interactive commands only
    
    These commands require a TTY and will NOT work - never use them:
    
    - `glab ci view` (interactive TUI) `(review-time: see section note)`
    - `gh run watch` (interactive watcher) `(review-time: see section note)`
    - Any command with `--web` flag (opens browser) `(review-time: see section note)`
    
    Safe commands to use:
    
    - `glab ci status`, `glab ci list`, `glab ci trace <job-id>` `(review-time: see section note)`
    - `gh pr checks`, `gh run list`, `gh run view <run-id> --log-failed` `(review-time: see section note)`
    
    ## Guardrails
    
    - After 3 consecutive failures on the **same issue**, stop and escalate - something structural is wrong `(review-time: see section note)`
    - Never weaken tests, skip linting, or lower coverage thresholds to make CI pass `(review-time: see section note)`
    - Never use `--no-verify` or skip hooks `(review-time: see section note)`
    - A failure unrelated to your changes (flaky test, infra issue) is transient: re-run it per step e, and do not edit code for it `(review-time: see section note)`
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.