github-workflow-doctor

Diagnose and repair failing GitHub Actions workflows by analyzing logs and applying fixes.

1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/waynebrantley/aitools --skill github-workflow-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-workflow-doctor
Source: https://github.com/waynebrantley/aitools/tree/main/plugins/ai-tools/skills/github-workflow-doctor
Command: npx skills add https://github.com/waynebrantley/aitools --skill github-workflow-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill tackles the frustration of broken GitHub Actions workflows by automatically diagnosing failures, attempting fixes, and re-running the workflow, saving developers significant debugging time.

Core Features & Use Cases

  • Automated Failure Analysis: Parses workflow logs to pinpoint the root cause of failures.
  • Intelligent Auto-Fixing: Applies common fixes for build, test, or configuration errors.
  • Iterative Retries: Automatically retries fixes up to three times, tracking new runs.
  • Use Case: A CI workflow fails due to a missing environment variable. This Skill detects the error, adds the variable to the configuration, commits the change, and re-runs the workflow until it passes.

Quick Start

Use the github-workflow-doctor skill to fix the latest failing GitHub workflow run.

Frequently Asked Questions about github-workflow-doctor

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

FAQPage Schema
How do I fix failing GitHub Actions workflows automatically?

To fix failing GitHub Actions workflows automatically, this Skill parses workflow logs to pinpoint root causes, applies targeted fixes to build or test configurations, commits changes via Git, and re-runs the workflow. It iterates this process up to three times until the pipeline passes.

Do I need the GitHub CLI to debug CI/CD pipeline failures?

Yes, you need the GitHub CLI (gh) installed to debug CI/CD pipeline failures with this tool. The GitHub CLI is required to interact with repository data, trigger new workflow runs, and track the status of iterative retries. Git is also necessary for committing configuration changes.

What types of CI/CD errors can be resolved through workflow automation?

Workflow automation can resolve CI/CD errors such as missing environment variables, build process failures, and test suite misconfigurations. It analyzes logs across various repository types to apply targeted fixes for common configuration and code errors automatically.

Can I use automated debugging for failed test suites across different repository types?

Yes, you can use automated debugging for failed test suites across various repository types. The Skill analyzes workflow logs to detect test failures, applies intelligent fixes to the code or configuration, and automatically re-runs the workflow to verify the resolution.

What are the limitations of automatically repairing GitHub Actions workflows?

A limitation of automatically repairing GitHub Actions workflows is that it restricts iterative retries to a maximum of three attempts. If the targeted fixes do not resolve the build or test failure within three automated runs, the process will stop and require manual intervention.