actions-debug

To debug failing GitHub Actions workflows, you analyze CI logs and YAML configuration files to identify root causes. Cross-referencing run logs with workflow YAML helps pinpoint misconfigurations like permission problems, missing secrets, timeouts, and cache issues.

GitHub Actions workflow timeouts and unexpected failures often stem from permission issues, missing secrets, or cache problems. Analyzing the specific run logs alongside the workflow YAML configuration helps identify the exact pattern causing the failure.

The best way to find root causes of flaky CI regressions is to analyze recent workflow run logs using GitHub CLI commands like gh run list and gh run view. Cross-referencing these outputs with YAML configurations surfaces actionable remediation steps.

Yes, GitHub CLI commands such as gh run list, gh run view, and log outputs can be used to diagnose GitHub Actions test failures and permission issues. These outputs are analyzed alongside YAML workflow files to pinpoint misconfigurations.

Log analysis cross-referenced with workflow YAML can detect common GitHub Actions misconfigurations including permission problems, missing secrets, cache misses, timeout triggers, and test failures, providing actionable fixes for each identified pattern.

To troubleshoot GitHub Actions errors with a run ID or workflow file name, use the actions-debug skill by running /actions-debug 12345678 or /actions-debug ci.yml to analyze the specific run logs and YAML configuration for that failure.