ci-review

Diagnosing GitHub Actions CI failures involves inspecting job logs to identify root causes like test failures or linting issues. This skill analyzes workflow runs and provides specific file paths and remediation steps to fix the errors.

GitHub Actions CI runs fail due to test errors, linting issues, type errors, or infrastructure problems. This skill inspects the failed run logs to pinpoint the exact cause and provides actionable code changes needed for remediation.

Yes, troubleshooting GitHub Actions workflow runs with this skill requires the gh CLI to interact with GitHub Actions. Understanding the workflow YAML is also necessary to provide proper context for the failure diagnosis.

Finding the root cause of a CI test failure is best done by inspecting the specific job logs. This skill automatically analyzes the GitHub Actions run to identify the failing test and explain where the fix is needed in the code.

Yes, you can automatically inspect a failed pull request CI check. This skill diagnoses the latest run on the current branch, identifies the failing component, and outputs clear remediation steps to fix the code.

CI failures that can be diagnosed from GitHub Actions logs include test failures, linting issues, type errors, and infrastructure problems. The diagnosis provides specific remediation steps for each identified root cause.