← ClaudeAtlas

ci-babysitlisted

Use after pushing a branch or opening a PR when CI needs monitoring or authorized make-green work. Keeps watch-only requests read-only, requires explicit current-request or approved-plan authority before reruns or local repairs, and stops honestly when a human or logic change is needed. Works in any ecosystem.
AndrewDongminYoo/cc-agents-kit · ★ 2 · DevOps & Infrastructure · score 71
Install: claude install-skill AndrewDongminYoo/cc-agents-kit
# CI Babysit Watch CI after a push until every job reaches a terminal state. Keep watch-only work read-only. Repair mechanical failures only when the current request or an approved plan gives explicit authority for local repair. ## When to use - Right after `git push`, `/ship`, or `/commit-push-pr` on a branch whose CI result gates the next step, such as merge, release, or a review request. - When the user asks to watch or monitor CI. - When the user explicitly asks to make CI green or approves a plan that includes local repair. Do NOT use for: local test runs (just run them), or repos without CI configured. ## Authority modes ### Watch-only A request to watch, monitor, or report CI is watch-only unless the same request or an approved plan explicitly authorizes changes. A watch-only request must not rerun jobs, install dependencies, format files, regenerate files, commit, or push. Read check state and logs, then report terminal failures without changing local or remote state. ### Make-green A make-green request must explicitly authorize state-changing reruns or local repair in the current request or an approved plan. Authority to rerun does not authorize local repair. Authority to repair does not authorize a commit or push. Require separate explicit authority for each commit and each push. ## Workflow ### 1. Identify what to watch ```bash branch_name=$(git branch --show-current) head_sha=$(git rev-parse HEAD) if ! pr_json=$(gh pr list --head "$branch_name" --state