Monitor GitHub Actions runs and diagnose red CI jobs after pushes.
npx skills add https://github.com/Bascht74/videopodcast-magic --skill ci-bascht74
Please help me install this Agent Skill. Skill: ci Source: https://github.com/Bascht74/videopodcast-magic/tree/main/.claude/skills/ci Command: npx skills add https://github.com/Bascht74/videopodcast-magic --skill ci-bascht74
tests/await_ci.sh as a harness-tracked background command that finds the run for HEAD and returns every job's verdict when it exits. - Failure triage: Decides whether a red job is the machine (missing tool, setup-step failure, runner-image sorting) or the code, then picks the smallest correct rerun (gh run rerun --job, --failed, or full) without pushing empty commits. - Post-green maintenance: Refreshes tests/state/longest via builder_times.sh, retargets stacked pull requests before deleting branches, and verifies merges before deletion. - Use Case: You pushed a commit and one of six matrix jobs (ubuntu/macos/windows on two Python versions) came back red. Use this Skill to wait for the full run, name the failed step, rule out flake causes, and rerun only the failed job before tagging a release. ## Quick Start After pushing a commit, run cd tests && bash await_ci.sh as a background command and wait for its verdict before doing anything else.High-intent search queries and answers about installing and using this skill.
Run tests/await_ci.sh as a background command tracked by the harness rather than a detached shell process. It locates the run belonging to HEAD, blocks until the run ends, and returns the verdict of every job when it exits.
Name the failed step first: setup-step failures and missing tools like ffmpeg or PySide6 indicate the machine, while suite-step failures indicate code. Failures sorting by runner image rather than platform, or hangs far past other jobs, also point to the machine.
No. Use gh run rerun with --job, --failed, or bare rerun to repeat the same commit, keeping the evidence tied to the state being tagged. A pushed commit changes the state and kills the run already in progress.
GitHub closes stacked pull requests whose base branch is deleted, and closed pull requests cannot be reopened or retargeted. Before deleting, retarget every open pull request standing on that branch with gh pr edit --base main.
Never on its own. A rerun answers only for that one job on that state, so after reruns carry a run to green, let one whole run pass on a single state before tagging. Six green jobs collected over multiple attempts is not valid release evidence.
jchildreeValidate git pushes with pre-push checks for large files and test failures.
MoofonLiAutomates versioned releases of the dev-ready package from version bump to PyPI publish.
PostHogDiagnoses failing GitHub Actions CI runs for PostHog pull requests and branches.
NaoyaMiyagawaRuns PHP and Laravel tests through Laravel Sail containers.