gh-fix-ci

Debug failing GitHub Actions checks by locating the relevant pull request, pulling run and job logs, and isolating key error lines to summarize the root cause. The skill automates this log inspection and triage process for current-branch pull requests or specified PR numbers.

Find the root cause of a CI failure by retrieving run and job logs from GitHub Actions and isolating key error lines and stack traces. This approach summarizes the specific error causing the workflow to fail without manual log hunting.

Yes, you need gh authentication to inspect failing GitHub Actions workflow runs. The skill requires gh authentication to access pull request data, retrieve workflow inspection logs, and initiate a post-fix recheck workflow.

No, you cannot use this to debug external CI providers. The scope is limited to GitHub Actions checks, meaning external CI providers are reported but not investigated for root cause analysis or fixes.

The approval-gated fixing process summarizes the root cause, proposes a focused fix plan, and waits for explicit user approval before making changes. It ensures you review and authorize any code modifications before implementation.

After implementing a fix for a failing GitHub Actions check, a post-fix recheck workflow is initiated. This verifies that the applied changes successfully resolve the original CI failure on the pull request.