actions-debug

Analyze GitHub Actions workflow failures and identify root causes from logs.

2|Updated Apr 6, 2017
One-click install
npx skills add https://github.com/shiiman/dotfiles --skill actions-debug-shiiman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: actions-debug
Source: https://github.com/shiiman/dotfiles/tree/main/ai/codex/skills/actions-debug
Command: npx skills add https://github.com/shiiman/dotfiles --skill actions-debug-shiiman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

GitHub Actions のワークフロー実行エラーを調査し、原因を特定して解決策を提案します。

Core Features & Use Cases

  • 失敗した Run の特定と関連 PR の checks の確認
  • エラーログの取得と原因分析、再現手順の提示
  • 修正案の提案と再実行の指示

Quick Start

Identify a recent failed workflow run, pull its logs, and propose concrete remediation steps.

Frequently Asked Questions about actions-debug

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

FAQPage Schema
How do I identify the root cause of a GitHub Actions workflow failure?

To identify the root cause of a GitHub Actions workflow failure, you analyze the failed run logs to find the exact error. This Skill extracts logs from failed jobs across test, build, dependency, and permission scenarios to pinpoint the failure point and propose deterministic remediation steps.

Why does my GitHub Actions build fail with a permission error?

GitHub Actions build permission errors often stem from insufficient token scopes or repository settings. This Skill analyzes permission scenario failures by extracting relevant workflow logs to determine the missing scopes and proposes actionable fixes to resolve the access issue.

Do I need the gh CLI to analyze GitHub Actions workflow errors?

Yes, you need the gh CLI installed and authenticated to analyze GitHub Actions workflow errors with this Skill. It requires gh CLI access to retrieve workflow logs and the necessary repository permissions to view the run history for extracting failure data.

What's the best way to fix dependency-related failures in CI/CD pipelines?

The best way to fix dependency-related failures in CI/CD pipelines is to analyze the package resolution errors in the workflow logs. This Skill examines dependency scenario failures from GitHub Actions runs to identify missing or conflicting packages and suggests concrete remediation steps.

Can I get reproduction steps for a failed GitHub Actions job?

Yes, you can get reproduction steps for a failed GitHub Actions job. After analyzing the error logs from the failed run, this Skill presents specific reproduction procedures to help you verify the issue locally before applying the proposed deterministic fixes.

GitHub Actions workflow errors not working with standard log viewers, what are the limitations?

Standard log viewers often lack the context to correlate GitHub Actions workflow errors with repository changes. This Skill overcomes limitations by pulling logs directly via the gh CLI to identify root causes across test, build, dependency, and permission scenarios for actionable fixes.