cilisted

# 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 ~/.claude/skills/ci/scripts/gh-ci-monitor.sh` `(review-time: see section note)` - GitLab: `bash ~/.claude/skills/ci/scripts/glab-ci-monitor.sh` `(review-time: see section note)` - Use `persistent: false`, `timeout_ms: 3600000` (1 hour ceiling - CI pipelines can be long) `(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)` - `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 `~/.claude/scripts/notify.sh "CI passed - <branch-name>"` `(review-time: see section note)` - Report success `(review-time: see section note)` - **Pipeline awaiting manual action** (`co