gh-fix-ci

To fix failing GitHub Actions checks on a pull request, you inspect failing runs, retrieve workflow or job logs, and extract failure context to determine if the issue is in test setup, build steps, or code changes.

Yes, authenticated gh access is required to retrieve GitHub Actions logs. The process relies on the GitHub CLI to pull workflow or job logs and apply resilient check-field fallbacks when identifying the relevant run details for your pull request.

Yes, it can summarize GitHub Actions logs for run-level and job-level failures. The process retrieves logs with run or job-level fallback handling to ensure it extracts the most useful failure snippet even if one log level is unavailable.

No, this does not work with non-GitHub Actions CI checks. Non-GitHub Actions checks are explicitly treated as out of scope, so the tool focuses entirely on diagnosing and planning fixes for GitHub Actions workflow failures.

The best way to triage a pull request failing in CI is to inspect failing GitHub Actions checks, pull the relevant workflow logs, summarize the failure context, and organize the issue into a clear fix plan before implementation.