skills.rest
tstapler
tstaplerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

github-actions-debugging

Diagnose GitHub Actions workflow failures from logs and error patterns.

8|2|Updated Jul 13, 2015
Search Tags:#automation#github-actions#ci-cd#root-cause#log-analysis#workflow-debugging#error-patterns
One-click install
npx skills add https://github.com/tstapler/dotfiles --skill github-actions-debugging-tstapler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-actions-debugging
Source: https://github.com/tstapler/dotfiles/tree/main/.claude/skills/github-actions-debugging
Command: npx skills add https://github.com/tstapler/dotfiles --skill github-actions-debugging-tstapler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

GitHub Actions failures can be opaque and time-consuming to diagnose. This skill analyzes workflow logs, identifies error patterns, and provides precise, actionable remediation steps to fix failures quickly.

Core Features & Use Cases

  • Pattern-based log analysis across syntax, dependencies, environment, permission, timeout, and network errors to pinpoint root causes.
  • Structured root-cause reports with recommended code changes, configuration tweaks, and verification steps.
  • Use cases include diagnosing job or step failures, timeouts, and intermittent flakiness in CI pipelines; works with multi-job matrices and composite actions.
  • Quick feedback loop: produce exact patch suggestions and test methods to validate fixes.

Quick Start

Provide the latest workflow log for a failing job to receive a structured debugging analysis.

Frequently Asked Questions about github-actions-debugging

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

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

Diagnose GitHub Actions failures by providing the failing job's workflow log to analyze error patterns, rank root causes, and output structured remediation steps with code patches.

Can I debug CI pipeline timeouts and intermittent flakiness in multi-job matrices?▼

Debug CI pipeline timeouts and intermittent flakiness in multi-job matrices by matching known error patterns across syntax, dependencies, environment, and network failures to pinpoint root causes.

What is the best way to find root causes for runner and composite action errors?▼

Find root causes for runner and composite action errors by applying pattern-based log analysis to extract context, rank probable causes, and generate deterministic remediation steps and code patches.

Does this workflow debugging approach provide exact code patches for CI fixes?▼

This workflow debugging approach provides exact code patch suggestions and test methods to validate fixes, producing structured root-cause reports with configuration tweaks and verification steps.

Why do my pull request workflows fail and how can I get actionable fixes?▼

Pull request workflows fail due to syntax, permission, dependency, or environment errors; get actionable fixes by analyzing logs to produce structured recommendations and exact code patches.

Related Skills

Explore More Software Engineering Skills→
ESO-ToolkitESO-Toolkit
2

debug-ci-failure

Debug failed GitHub Actions CI runs by identifying the failed stage and root cause.

Official
Advanced
0x0pointer0x0pointer
13

remediate

Generate implementable remediation patches for findings in findings.json.

Official
Advanced
tanyagraytanyagray

gitlab-ci

Manage GitLab CI/CD pipelines and jobs using the glab CLI.

Community
Intermediate
HomericIntelligenceHomericIntelligence
18

analyze-ci-failure-logs

Parse and categorize CI failure logs to identify root causes.

Official
Intermediate