fix-ci-failures

To fix failing CI checks, you list the failed GitHub Actions jobs, download the specific job logs, isolate the exact failing step or error annotation, and apply the smallest safe code fix. This distinguishes actual code regressions from flaky infrastructure failures.

GitHub Actions checks fail due to code regressions, build errors, test crashes, or environment issues. You identify the exact cause by downloading job logs and inspecting artifacts to review specific error annotations and failing steps.

Yes, you need the gh CLI installed and authenticated. Access to the pull request branch, job logs, and run artifacts is required to detect the PR, list checks, download logs, and validate iterative recovery reruns.

You download GitHub Actions logs and artifacts by targeting the associated pull request branch, isolating the failed jobs, and extracting the logs to inspect test failures, build errors, crashes, and environment issues.

Determine if a CI failure is flaky or a real regression by inspecting job logs and artifact outputs for environment issues versus code errors. Iterative recovery supports reruns to validate if the failure persists after applying a safe fix.