← ClaudeAtlas

ci-status-snapshotlisted

Token-efficient GitLab CI, GitHub Checks, MR, and PR status handling with one-shot snapshots or a silent local watcher that notifies the agent only when state changes. Use when the user asks whether CI passed, wants an active goal to continue through CI/review waits, asks to merge after checks, wants provider auto-merge, or corrects model-driven polling.
Wisdoverse/ci-status-snapshot · ★ 1 · Code & Development · score 72
Install: claude install-skill Wisdoverse/ci-status-snapshot
# CI Status Snapshot `$SKILL_DIR` means this skill's install directory — the one holding this `SKILL.md`. Installed as a plugin it is the host's plugin cache directory, which Claude Code and Codex report when the skill loads; copied manually it is `~/.claude/skills/ci-status-snapshot` or `~/.codex/skills/ci-status-snapshot`. Substitute it or export it once; never hardcode an install layout. This file is the always-loaded contract. Two playbooks stay unloaded until their trigger fires: `$SKILL_DIR/references/gitlab-triage.md` (failed/stuck GitLab jobs) and `$SKILL_DIR/references/merge-flow.md` (merge and auto-merge delegation). ## Goal Use compact one-shot snapshots for immediate questions. When an active goal depends on pending CI or review, arm the bundled local watcher in an attached deferred tool call — it polls without model turns and emits one compact event when state changes — and let provider-side auto-merge own the merge itself. Efficiency here means token budget control: fewer CLI calls, narrower reads, fewer chat turns. ## Agent/Watcher Contract The authoritative rule list. Everything below is binding. - Hard rule: the agent never runs the polling loop. No repeated tool calls or assistant turns, `--watch` commands that stream progress into chat, scheduled goal turns or continuations, subagents, reminders, terminal streams, status narration, or manual "check again" cycles. A deterministic local script may poll while the model is idle, provided it stays silent