fix-ci

To fix failing GitHub Actions checks, use `gh pr checks` to identify the earliest actionable failing job, inspect its logs to diagnose the root error, apply a small safe fix, and re-check until all relevant checks pass.

Pull request CI fails when specific jobs encounter errors. You can find the root cause by running `gh pr checks --json name,bucket,state,workflow,link`, inspecting the failed job details, and following external links to the relevant logs.

The best way to diagnose multiple failing PR checks iteratively is to locate the first red job using `gh pr checks` as the source of truth, resolve one actionable failure at a time with minimal changes, and repeat the process until CI is green.

Yes, you need the GitHub CLI to inspect failed job details for CI debugging, as this Skill requires using `gh pr checks` output as the source of truth to locate the specific job that is red and retrieve its check link.

Yes, you can resolve GitHub Actions failures without unnecessary refactors by applying the smallest safe change iteratively, ensuring each push resolves exactly one actionable failure at a time to reach a green build.

You should avoid applying multiple fixes at once during CI debugging when following an iterative PR workflow, because applying the smallest safe change one at a time ensures a minimal-change path back to green without introducing new errors.