Agent skill · AI & Agents

fix-failing-pipelines

This skill should be used when the user asks to "fix pipelines", "fix CI", "check staging pipelines", "fix failing workflows", "fix failing actions", or wants to find and fix failing GitHub Actions workflows on the staging branch of the babysitter repo.

a5c-aigithub.com/a5c-aiGitHub ↗
claude-codecodexMIT
Install
npx skills add a5c-ai/babysitter --skill fix-failing-pipelines --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: .claude/skills/fix-failing-pipelines/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,642
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Fix Failing Pipelines Check GitHub Actions workflows on the `staging` branch of https://github.com/a5c-ai/babysitter/actions, identify workflows whose most recent run is failing, and dispatch `/babysitter:yolo` to fix each one. ## Workflow ### Step 1: Fetch Most Recent Run Per Workflow Use the `gh` CLI to list recent workflow runs on the `staging` branch: ```bash gh run list --repo a5c-ai/babysitter --branch staging --limit 50 --json databaseId,workflowName,status,conclusion,createdAt,headBranch ``` Group the results by `workflowName`. For each workflow, keep only the **most recent** run (by `createdAt`). Discard workflows where the most recent run is still `in_progress` -- we only care about completed runs. ### Step 2: Identify Failures From the grouped results, select only workflows where the most recent completed run has `conclusion: "failure"`. Skip workflows whose latest run succeeded, was cancelled, or is still running. If no workflows have a failing most-recent run, report that all staging pipelines are green and stop. ### Step 3: Get Failure Details For each failing workflow run, fetch the failed job and step details: ```bash gh run view <run_id> --repo a5c-ai/babysitter

What's inside
Steps it walks through
  1. Workflow
  2. Step 1: Fetch Most Recent Run Per Workflow
  3. Step 2: Identify Failures
  4. Step 3: Get Failure Details
  5. Step 4: Present Failures
  6. Step 5: Fix via Babysitter
  7. Step 6: Verify Fixes
  8. Step 7: Summary
  9. Notes
Commands it runs
gh run list --repo a5c-ai/babysitter --branch staging --limit 50 --json databaseId,workflowName,status,conclusion,createdAt,headBranch
gh run view <run_id> --repo a5c-ai/babysitter --log-failed 2>&1 | tail -100
gh run list --repo a5c-ai/babysitter --branch staging --workflow "<workflow_file>" --limit 1 --json databaseId,status,conclusion
More from babysitter
All skills →
About this skill
What does the fix-failing-pipelines skill do?

This skill should be used when the user asks to "fix pipelines", "fix CI", "check staging pipelines", "fix failing workflows", "fix failing actions", or wants to find and fix failing GitHub Actions workflows on the staging branch of the babysitter repo.

How do I install it?

Run `npx skills add a5c-ai/babysitter --skill fix-failing-pipelines --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From a5c-ai/babysitter, a repository with 1,642 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going