diagnose-ci

You can diagnose GitHub Actions CI failures on self-hosted runners by running the /ci:diagnose command with a specific run-id. This identifies the failure pattern and provides actionable remediation steps to fix the workflow.

Common GitHub Actions failure patterns for self-hosted runners are categorized as F01 through F12. This diagnostic tool provides a catalog of these failure patterns alongside troubleshooting strategies to identify and resolve environment-specific CI issues.

You can check the health of your self-hosted CI runner by using the /ci:runner-health command. This function performs runner-health checks and offers quick runbook references to troubleshoot environment drift and infrastructure issues.

Yes, you can troubleshoot environment drift issues in GitHub Actions workflows. The diagnostic process includes quick runbook references specifically designed to address common runner-health and environment-drift problems on self-hosted infrastructure.

The best way to get a quick status overview of a failing CI pipeline is to use the /ci:status command. This accelerates debugging by integrating with common CI tooling to report on the current state of your workflows.

A failure pattern catalog may not be suitable if your CI issue stems from a unique application logic error rather than infrastructure or environment drift. This diagnostic approach is optimized for self-hosted runner failures and GitHub Actions workflow troubleshooting.