gh-fix-ci

Debugging failing GitHub Actions checks involves mapping the PR check failure to the specific run and job, then extracting the relevant log snippet. This Skill automates resolving the PR number, fetching run metadata via gh, and extracting the failure log.

Yes, retrieving GitHub Actions logs includes fallbacks when fields drift or logs are pending. The Skill handles delayed log retrieval by capturing concise failure snippets and gracefully managing pending states during the run inspection.

Finding the failing GitHub Actions job requires fetching the PR status to extract run and job identifiers. This Skill uses the gh CLI to authenticate, fetch check statuses, and isolate the exact job metadata needed for deeper log inspection.

No, this workflow does not automatically apply fixes to failing GitHub PR checks. It produces a summarized failure snippet and an actionable fix plan, then explicitly waits for your approval before any implementation or code changes are made.

No, you cannot use this to debug CI failures from non-GitHub providers like Jenkins or GitLab. The Skill explicitly treats non-GitHub CI providers as out of scope, focusing solely on GitHub Actions run log analysis and checks.