gh-fix-ci

To debug failing GitHub Actions PR checks, you fetch the workflow logs via the gh CLI, inspect the failure details, and summarize the context to identify the root cause before drafting any code changes.

The best way to summarize GitHub Actions logs is to fetch them directly via gh authentication, surface actionable failure details, and generate a concise, approval-ready fix plan for the repository.

Yes, you need gh authentication and repository access to read PR checks and fetch GitHub Actions logs. Without proper gh CLI authentication, you cannot inspect the failing workflows or generate a fix plan.

No, this approach does not work with external CI providers like Buildkite. It applies only to GitHub-hosted workflows and PR checks, reporting only the details URL for external providers instead of fetching their logs.

To ensure safe implementation of fixes for failing GitHub PR checks, the workflow requires explicit user approval before implementing any changes to the repository based on the drafted fix plan.