starwards-ci-debugging

Download and analyze CI logs automatically using GitHub CLI. This skill fetches your workflow run logs, parses ESLint, TypeScript, Playwright, and Docker errors, identifies root causes, and guides you toward reproducible fixes you can verify locally before pushing.

Yes. GitHub CLI retrieves all logs from a specific workflow run. This skill automates that retrieval and systematically analyzes them to pinpoint ESLint linting errors, TypeScript compilation failures, Playwright browser test mismatches, and Docker build problems.

This skill targets ESLint violations, TypeScript type errors, unit and end-to-end test failures (including Playwright browser version mismatches), and Docker or build workflow errors—the most common blockers in GitHub Actions pipelines.

Download the failure logs, identify the exact error (e.g., a Playwright browser incompatibility), apply the fix locally, verify it passes the same checks, then push. This skill automates log retrieval and error parsing to accelerate that cycle.

You need GitHub CLI (gh) installed and configured. This skill uses it to fetch logs from your GitHub Actions workflows, eliminating the need to manually navigate the GitHub UI for each failure.

Use GitHub CLI to download logs immediately, pinpoint the specific error category (ESLint, TypeScript, test, or build), apply a targeted fix, and verify locally. This skill streamlines that entire diagnosis-and-fix loop.