starwards-ci-debugging

Name: starwards-ci-debugging
Availability: InStock
Author: Starwards

Diagnose Starwards GitHub Actions CI failures from downloaded logs.

42|2|Updated Mar 17, 2019

Search Tags:#automation #debugging #CI/CD #troubleshooting #logs #GitHub Actions #starwards

Ready to run

npx skills add https://github.com/starwards/starwards --skill starwards-ci-debugging

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: starwards-ci-debugging
Source: https://github.com/starwards/starwards/tree/main/.claude/skills/starwards-ci-debugging
Command: npx skills add https://github.com/starwards/starwards --skill starwards-ci-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solves? GitHub Actions CI failures can block development, and debugging them without proper tools is frustrating and time-consuming. This skill provides a systematic approach to diagnose and fix Starwards CI failures by leveraging GitHub CLI to download and analyze logs.

Core Features & Use Cases

Automated Log Retrieval: Quickly download all CI logs for a specific workflow run using GitHub CLI.
Targeted Log Analysis: Guides through identifying ESLint, TypeScript, Playwright, and build errors within the downloaded logs.
Use Case: When a pull request fails CI, use this skill to immediately download the logs, pinpoint the exact error (e.g., a Playwright browser version mismatch), and apply the correct fix without guesswork.

Quick Start

"My PR #1234 has failing CI checks. Help me debug the failures."

Frequently Asked Questions about starwards-ci-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I debug GitHub Actions CI failures without manually inspecting logs?▼

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.

Can I use GitHub CLI to extract logs from a failing pull request?▼

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.

What types of CI errors can this skill help me diagnose?▼

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.

How do I fix a CI failure locally before resubmitting my PR?▼

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.

Do I need any tools installed to debug CI failures with this approach?▼

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.

What's the fastest way to unblock a PR stuck on CI checks?▼

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.