resolve-ci-failures

Investigate CI/CD failures and coordinate approved fixes for GitHub Actions pipelines.

4|5|Updated Feb 20, 2026

Search Tags:#debugging #github-actions #workflow-automation #ci #ci-failures #gh-cli

Ready to run

npx skills add https://github.com/fartybobo/farty-bobo --skill resolve-ci-failures

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: resolve-ci-failures
Source: https://github.com/fartybobo/farty-bobo/tree/main/skills/resolve-ci-failures
Command: npx skills add https://github.com/fartybobo/farty-bobo --skill resolve-ci-failures

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents CI/CD regressions from blocking releases by guiding AI to investigate failing jobs on the current branch or PR, diagnose root causes, and coordinate approved remediation before rerunning the pipeline.

Core Features & Use Cases

Failing job discovery: Use the GitHub CLI to list runs, view failures, and inspect logs so the AI can see exactly what broke.
Failure categorization: Classify issues as lint, type, test, build, or infrastructure problems, flagging unstable environments for human attention while resolving deterministic ones automatically.
Coordinated remediation: Summarize the failures, propose fixes for approval, assign focused agent tasks, run full-project checks, issue a /critique, and monitor the subsequent CI run to confirm success.

Quick Start

Ask resolve-ci-failures to gather the current branch's failing CI jobs and outline the fixes.

Frequently Asked Questions about resolve-ci-failures

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I debug GitHub Actions failures blocking my pull request?▼

To debug GitHub Actions failures, this Skill fetches failed job logs using the gh CLI, categorizes the root cause as lint, type, test, build, or infrastructure issues, and proposes targeted fixes for approval before rerunning the pipeline.

Can I automatically rerun CI jobs after applying code fixes?▼

You can automatically rerun CI jobs after fixes by having the Skill run full-project checks, issue a critique, and monitor the subsequent GitHub Actions run to confirm the pipeline succeeds without requiring manual triggers.

What is the best way to categorize CI failures for automated remediation?▼

The best way to categorize CI failures is to parse the failed job logs and classify issues into deterministic types like lint, type, test, or build errors for automated fixes, while flagging unstable infrastructure problems for human intervention.

Does this Skill require human approval for all GitHub Actions pipeline fixes?▼

This Skill does not require human approval for all fixes; it automatically resolves deterministic lint, type, test, and build errors, but explicitly requires human approval for non-infrastructure fixes and unstable environments.

Why use the GitHub CLI to investigate failing CI/CD workflows?▼

Using the GitHub CLI to investigate failing CI/CD workflows allows the Skill to execute commands like 'gh run view --log-failed' to fetch exact failure logs, enabling accurate diagnosis and coordinated remediation tied to the current branch context.

What should I do when CI regressions block my deployment?▼

When CI regressions block deployment, you should gather the current branch's failing jobs, summarize the categorized failures, assign focused agent tasks to apply approved fixes, and monitor the next CI run to verify success.