How do I install the CI Watch skill?

Run npx skillmds@latest add lucassantana-dev/ci-watch in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is CI Watch safe to use?

SkillMD's automated safety review verdict for this skill is PASS. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with CI Watch?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is CI Watch free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published CI Watch?

LucasSantana-Dev (@lucassantana-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

CI Watch by lucassantana-dev — Agent Skill

Name: CI Watch
Rating: 4.2 (5 reviews)
Author: LucasSantana-Dev

File contents

ci-watch

Use for broken checks, flaky tests, or merge-blocking pipeline noise.

Phases

Phase 1 — Triage

Identify the active PR or HEAD commit.
List non-passing checks.
Separate required failures from advisory noise.

Read PR state: gh pr view N --json mergeable,mergeStateStatus,reviewDecision,statusCheckRollup

Phase 2 — Diagnose

Inspect the first failing required job deeply (logs, not just the summary line).
Name the smallest fix — or the exact reason the failure is pre-existing / unrelated to the current change.

Phase 3 — Fix or Monitor

If fixable: apply smallest fix, push, watch checks settle.
If not fixable now: document the blocker and surface it as output.
For checks that take >1 min to settle: use a Monitor until-loop rather than busy-waiting.

Output

BLOCKED — <job name>: <one-line cause>
  Fix: <smallest concrete action>
  Blocks shipping: yes / no

CLEAR — all required checks green

Reconciliation

CI WATCH — <PR/SHA>

Phase 1 Triage:   N failing checks (<X> required, <Y> advisory) ✅
Phase 2 Diagnose: root cause: <description> ✅
Phase 3 Fix:      <action taken> | (blocked: <reason>) ✅

Result: RESOLVED | BLOCKED (requires: <what unblocks it>)

PR state machine

mergeable / state	Action
`MERGEABLE` + `CLEAN`	proceed to merge
`MERGEABLE` + `UNSTABLE`	non-required check failing; poll required-only checks
`MERGEABLE` + `BEHIND`	`gh pr update-branch` or local rebase + force-push
`MERGEABLE` + `BLOCKED`	check `reviewDecision` and branch protection
`CONFLICTING` + `DIRTY`	local rebase first; if GH disagrees → webhook desync, close+recreate
`UNKNOWN` + `UNKNOWN`	wait 15s, recheck; if STILL UNKNOWN try `gh pr merge` directly

Common gotchas

UNKNOWN often means the PR was already merged in another window.
mergeStateStatus: BLOCKED with no failing checks = review or branch protection.
PR head SHA disagrees with git ls-remote = webhook desync. Close + recreate.

---name: ci-watchdescription: Inspect current CI state, identify the first real blocker, separate required failures from noise, and monitor until checks settle. Use when checks are failing, flaky, or blocking a merge.---# ci-watchUse for broken checks, flaky tests, or merge-blocking pipeline noise.## Phases### Phase 1 — Triage1. Identify the active PR or HEAD commit.2. List non-passing checks.3. Separate required failures from advisory noise.Read PR state: `gh pr view N --json mergeable,mergeStateStatus,reviewDecision,statusCheckRollup`### Phase 2 — Diagnose4. Inspect the first failing required job deeply (logs, not just the summary line).5. Name the smallest fix — or the exact reason the failure is pre-existing / unrelated to the current change.### Phase 3 — Fix or Monitor6. If fixable: apply smallest fix, push, watch checks settle.7. If not fixable now: document the blocker and surface it as output.8. For checks that take >1 min to settle: use a Monitor until-loop rather than busy-waiting.## Output```BLOCKED — <job name>: <one-line cause> Fix: <smallest concrete action> Blocks shipping: yes / noCLEAR — all required checks green```## Reconciliation```CI WATCH — <PR/SHA>Phase 1 Triage: N failing checks (<X> required, <Y> advisory) ✅Phase 2 Diagnose: root cause: <description> ✅Phase 3 Fix: <action taken> | (blocked: <reason>) ✅Result: RESOLVED | BLOCKED (requires: <what unblocks it>)```## PR state machine| mergeable / state | Action ||---|---|| `MERGEABLE` + `CLEAN` | proceed to merge || `MERGEABLE` + `UNSTABLE` | non-required check failing; poll required-only checks || `MERGEABLE` + `BEHIND` | `gh pr update-branch` or local rebase + force-push || `MERGEABLE` + `BLOCKED` | check `reviewDecision` and branch protection || `CONFLICTING` + `DIRTY` | local rebase first; if GH disagrees → webhook desync, close+recreate || `UNKNOWN` + `UNKNOWN` | wait 15s, recheck; if STILL UNKNOWN try `gh pr merge` directly |## Common gotchas- `UNKNOWN` often means the PR was already merged in another window.- `mergeStateStatus: BLOCKED` with no failing checks = review or branch protection.- PR head SHA disagrees with `git ls-remote` = webhook desync. Close + recreate.

Frequently asked questions

CI Watch