gh-fix-ci

To debug failing GitHub Actions checks, the skill fetches PR metadata and uses the GitHub CLI to retrieve logs, extracts the failure snippet, summarizes root causes, and proposes a fix plan requiring your approval before applying changes.

No, you cannot automatically apply changes without manual review. This CI debugging workflow requires explicit user approval before implementing any proposed fixes to ensure guardrails and safe validation in production-like environments.

You need to authenticate with the GitHub CLI and have the GitHub App provide PR metadata. The workflow then fetches check data and logs from repositories where GitHub Actions checks are currently failing.

Log inspection retrieves failing run data via the GitHub CLI and surfaces concise failure context by extracting snippets. This automated log retrieval speeds up root cause analysis and focused remediation for your pull requests.

Yes, the workflow generates a summarized root cause by fetching check data and extracting failure snippets from GitHub Actions logs. It then presents a focused fix plan based on this analysis for your review.

The best way to handle GitHub Actions PR check failures safely is using an approval-based workflow that extracts failure context, summarizes root causes, and supports step-by-step validation before applying any code changes.