gh-fix-ci

Diagnosing failing GitHub Actions checks involves inspecting PR runs to collect metadata and extracting relevant failure snippets from logs. The automation summarizes actionable context to help you decide on a focused remediation plan without manually hunting through logs.

Yes, you can extract failure context automatically by running a helper script that fetches workflow run logs. It identifies failing jobs, extracts the relevant snippet, and summarizes the actionable context for reviewer approval before implementing changes.

Yes, authenticated gh CLI access is required to inspect GitHub Actions workflow runs and logs. The Skill applies gh CLI commands to the repository, requiring your permission to view checks and fetch log data for analysis.

External CI providers are detected, labeled as out of scope, and reported by URL only. Diagnosing PR check failures focuses on GitHub Actions runs, fetching and summarizing internal logs while simply linking to external provider details.

The best way to fix failing GitHub Actions CI without manual log reading is to use a script that fetches workflow runs, identifies failing jobs, and extracts failure snippets. This produces a concise summary and a proposed fix plan for approval.