skills.rest
jdconley
jdconleyCOMMUNITY
Explore all skills by this author →
Website𝕏@wackieGitHub

debug-ci-workflows

Debug failing GitHub Actions CI workflows and Playwright E2E tests.

1|Updated Jan 27, 2026
Search Tags:#debugging#deployment#github actions#playwright#e2e testing#ci
One-click install
npx skills add https://github.com/jdconley/wodbrains --skill debug-ci-workflows
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-ci-workflows
Source: https://github.com/jdconley/wodbrains/tree/main/.cursor/skills/debug-ci-workflows
Command: npx skills add https://github.com/jdconley/wodbrains --skill debug-ci-workflows

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps diagnose and resolve issues in GitHub Actions CI workflows, particularly those related to deployment and end-to-end Playwright tests that are failing or hanging.

Core Features & Use Cases

  • CI Failure Triage: Quickly inspect logs and job statuses of failing GitHub Actions runs.
  • Local Reproduction: Set up environments (Docker, act) to reliably reproduce CI failures locally.
  • Playwright Debugging: Address common Playwright issues like web server readiness timeouts and browser launch failures in CI.
  • Use Case: When your deploy.yml workflow fails in GitHub Actions, use this Skill to pinpoint the exact error, reproduce it on your local machine, and implement a fix.

Quick Start

Use the debug-ci-workflows skill to inspect the logs of a failing GitHub Actions run with ID '1234567890'.

Frequently Asked Questions about debug-ci-workflows

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

FAQPage Schema
How do I debug failing GitHub Actions workflows for deployment and Playwright E2E tests?▼

Debug failing GitHub Actions workflows by using `gh` CLI commands for fast triage, reproducing failures locally with Docker or `act`, and applying specific strategies for Playwright webServer and flaky test issues.

Why does my Playwright E2E test hang in CI due to webServer timeout?▼

Playwright E2E test webServer hangs in CI often stem from server readiness timeouts or browser launch failures; this Skill provides specific strategies to resolve missing browser installations and server readiness blocks.

How can I reproduce GitHub Actions CI failures locally?▼

Reproduce GitHub Actions CI failures locally by setting up environments using Docker or the `act` tool to reliably mirror the deployment and test execution conditions before implementing a fix.

What is the best way to triage failing GitHub Actions runs?▼

The best way to triage failing GitHub Actions runs is using `gh` CLI commands to quickly inspect logs and job statuses, allowing you to pinpoint the exact deployment or Playwright test error.

How do I fix missing Playwright browser installations in GitHub Actions CI?▼

Fix missing Playwright browser installations in GitHub Actions CI by following targeted debugging strategies that address common browser launch failures and ensure web server readiness during E2E test execution.

Related Skills

Explore More Software Engineering Skills→
ericmjlericmjl
38

debug-github-ci

Debug GitHub Actions CI failures using gh CLI to inspect runs, logs, and workflows.

Community
Advanced
YuriNakayamaYuriNakayama

E2E Fix

Diagnose and fix failing Playwright E2E tests in GitHub Actions CI.

Community
Advanced
w020316w020316

testing-devops

Automate testing and operations workflows for software projects.

Community
Intermediate
noir-langnoir-lang
1.4k

extract-fuzzer-repro

Convert GitHub Actions fuzzer failure logs into a minimal Noir reproduction project.

Official
Advanced