gha

Diagnose the latest GitHub Actions workflow failure using gh CLI logs.

79|33|Updated Jul 2, 2026
One-click install
npx skills add https://github.com/thiagofinch/mega-brain --skill gha-thiagofinch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gha
Source: https://github.com/thiagofinch/mega-brain/tree/main/.claude/skills/gha
Command: npx skills add https://github.com/thiagofinch/mega-brain --skill gha-thiagofinch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub Actions failures are often opaque; this skill identifies the latest failed workflow, collects logs, and surfaces likely root causes to speed remediation.

Core Features & Use Cases

  • Automatic detection of the most recent failing workflow run
  • Log retrieval, pattern-based root-cause analysis, and actionable fix suggestions
  • Guidance for manual debugging with common gh CLI commands

Quick Start

Ask me to run /gha to inspect the latest failed GitHub Actions workflow.

Frequently Asked Questions about gha

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

FAQPage Schema
How do I diagnose GitHub Actions failures from CI logs?

To diagnose GitHub Actions failures, this skill automatically detects the latest failed workflow run, retrieves CI logs, and applies pattern-based root-cause analysis to suggest actionable fixes for build, test, or lint errors.

What is the best way to troubleshoot a failing GitHub Actions workflow run?

The best way to troubleshoot a failing GitHub Actions workflow run is to use this skill, which parses workflow logs and applies deterministic heuristics to pinpoint root causes and speed up remediation.

Do I need the gh CLI installed to analyze my GitHub Actions logs?

Yes, you need the gh CLI installed and authenticated, because this skill uses gh CLI outputs to retrieve logs and identify the most recent failing workflow run across your CI pipelines.

Can I find the root cause of a build failure automatically in GitHub Actions?

Yes, you can find the root cause of a build failure automatically by triggering this skill, which retrieves the latest GitHub Actions logs and uses pattern-based analysis to surface likely root causes.

What gh CLI commands should I use for manual debugging of CI pipelines?

For manual debugging of CI pipelines, this skill provides guidance on common gh CLI commands alongside its automatic log retrieval and pattern-based root-cause analysis for failed GitHub Actions workflows.