fix-ci

Use `gh pr checks` to pull the failing job details, extract the first actionable error from the logs, apply the smallest safe fix to your pull request, and iterate with re-checks until the GitHub Actions checks pass.

The best way to debug CI build failures is to locate the first actionable error in the failed job logs, apply one low-risk minimal change at a time, and re-check the PR until the checks are green.

Yes, this approach works with GitHub Actions check sets by using `gh pr checks` as the source of truth and utilizing the provided logs or check links to identify the failing command or service.

You locate the root cause of a failed GitHub Actions job by extracting the first actionable error from the failed job logs or check link, rather than manually reviewing the entire build output.

Applying minimal fixes when resolving CI build failures ensures you make one low-risk change at a time, maintaining clear accountability of what was changed while safely iterating towards a green PR.

You should avoid automated iterative repair for CI failures if your GitHub Actions workflows do not rely on standard check sets or if `gh pr checks` cannot access the logs needed to identify the failing command.