CI Diagnosis

To diagnose GitHub Actions build failures, this Skill pinpoints the exact failed step and error message in your CI runs. It analyzes the workflow logs to identify the root cause of build, push, and manifest creation issues, providing targeted fix recommendations.

GitHub Actions workflows fail during skopeo push or crane manifest creation due to registry authentication, image layer, or manifest configuration errors. This Skill troubleshoots these specific CI failures, extracting the error message and providing recommendations to resolve the push and manifest issues.

Yes, you need the gh CLI installed to troubleshoot failed CI runs with this Skill. It requires the GitHub CLI to interact directly with your GitHub Actions runs, fetch workflow logs, and identify the root cause of the build errors.

Yes, you can use this to find the root cause of workspace build failures in your pull requests. It specifically covers build-workspace.yaml pipelines, analyzing the failed CI run to isolate the exact step, clarify unclear errors, and recommend specific fixes.

The best way to fix unclear build errors in a build-openclaw.yaml pipeline is to use a diagnostic tool that pinpoints the exact failed step. This Skill investigates the failed GitHub Actions run, identifies the root cause, and provides actionable fix recommendations to unblock your development.

Your GitHub Actions CI run is not working because of build, push, or manifest creation errors introduced by the code change. This Skill diagnoses the most recent failed run, isolates the specific error message, and recommends fixes to resolve the pipeline blockage.