gha-diagnosis

Name: gha-diagnosis
Availability: InStock
Author: Provectus

Diagnoses and fixes GitHub Actions workflow failures using gh CLI.

10|17|Updated Feb 22, 2026

Search Tags:#automation #workflow #ci/cd #debugging #troubleshooting #github actions

Ready to run

npx skills add https://github.com/provectus/awos-recruitment --skill gha-diagnosis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gha-diagnosis
Source: https://github.com/provectus/awos-recruitment/tree/main/registry/skills/gha-diagnosis
Command: npx skills add https://github.com/provectus/awos-recruitment --skill gha-diagnosis

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automatically diagnoses and fixes failures in GitHub Actions workflows, reducing manual debugging time and ensuring CI/CD pipeline health.

Core Features & Use Cases

Automated Failure Triage: Identifies root causes of CI failures from logs.
Intelligent Fixing: Applies targeted fixes based on common failure categories (lint, test, build, etc.).
Local Verification: Verifies fixes locally before committing.
Use Case: When your GitHub Actions pipeline shows red, this Skill can automatically investigate, fix the underlying issue, and push the solution.

Quick Start

Use the gha-diagnosis skill to fix the failing GitHub Actions run.

Frequently Asked Questions about gha-diagnosis

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

FAQPage Schema

How do I fix GitHub Actions workflow failures automatically?▼

To fix GitHub Actions failures automatically, the gha-diagnosis Skill fetches CI/CD logs via the gh CLI, triages root causes like linting or build errors, applies targeted fixes, and verifies them locally before pushing.

What types of CI/CD pipeline errors can be diagnosed through this automated troubleshooting approach?▼

Automated troubleshooting for CI/CD pipelines addresses common GitHub Actions failures, including linting errors, testing failures, build breakdowns, and environment misconfigurations identified directly from workflow logs.

Do I need the gh CLI installed to diagnose GitHub Actions failures locally?▼

Yes, you need the gh CLI installed to diagnose GitHub Actions failures, as the Skill depends on it to fetch workflow logs and run local verification of the applied fixes against workflow YAML commands.

How do I verify GitHub Actions fixes locally before committing to the repository?▼

To verify GitHub Actions fixes locally before committing, the Skill executes the workflow YAML commands directly in your local environment using the gh CLI to ensure the resolved build or test failure does not persist.

What is the best way to troubleshoot GitHub Actions environment misconfigurations without manual log parsing?▼

The best way to troubleshoot GitHub Actions environment misconfigurations without manual log parsing is using an automated diagnosis Skill that fetches logs via gh CLI and intelligently applies fixes based on failure categories.

Why does my GitHub Actions workflow still fail after an automated fix is applied?▼

GitHub Actions workflows may still fail after an automated fix if the local verification step did not accurately replicate the CI environment, or if the failure category falls outside standard lint, test, and build error patterns.