skills.rest
guillempuche
guillempucheCOMMUNITY
Explore all skills by this author →
GitHub

playwright-devops

Collect and group failed GitHub Actions logs for Playwright CI commits.

6|1|Updated Apr 1, 2026
Search Tags:#automation#devops#logs#playwright#github-actions#ci#workflow-analysis
One-click install
npx skills add https://github.com/guillempuche/batuda --skill playwright-devops
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: playwright-devops
Source: https://github.com/guillempuche/batuda/tree/main/docs/repos/playwright/.claude/skills/playwright-devops
Command: npx skills add https://github.com/guillempuche/batuda --skill playwright-devops

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq.

What problem does it solve?

CI failures in Playwright pipelines can stall development and obscure root causes; this skill provides structured guidance to collect, group, and analyze failed runs to accelerate debugging and release readiness.

Core Features & Use Cases

  • CI failure analysis and log collection for GitHub Actions
  • Step-by-step debugging guidance and reference scripts (commit-failures.md, fetch-commit-logs.sh)
  • Structured summaries suitable for post-mortems and automation

Quick Start

Run the fetch-commit-logs.sh script to download failed GitHub Actions logs for a commit and organize them locally for analysis.

Frequently Asked Questions about playwright-devops

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

FAQPage Schema
How do I analyze Playwright CI failures in GitHub Actions?▼

To analyze Playwright CI failures, this skill collects and groups failed GitHub Actions logs for a specific commit, generating a structured failure summary to accelerate debugging and release readiness.

What's the best way to collect failed GitHub Actions logs for a commit?▼

The best way to collect failed logs is running the fetch-commit-logs.sh script, which downloads and organizes failed GitHub Actions logs locally for a given commit to streamline pipeline debugging.

Do I need the GitHub CLI and jq to parse GitHub Actions logs?▼

Yes, you need the GitHub CLI (gh) and jq installed, as this skill relies on them to fetch, parse, and format failed GitHub Actions logs for Playwright pipeline analysis.

Can I use this for debugging flaky pipelines across releases and maintenance?▼

Yes, this skill is suitable for debugging flaky pipelines across main branches, releases, and ongoing maintenance by providing structured summaries of failed runs suitable for post-mortems.

How does grouping failed GitHub Actions logs help with CI debugging?▼

Grouping failed logs helps CI debugging by organizing scattered error data into a structured failure summary, making it easier to identify root causes and accelerate release readiness.

Related Skills

Explore More Software Engineering Skills→
openkaidenopenkaiden
3

update-github-action

Resolve GitHub Actions tags to immutable commit SHAs for workflow steps.

Official
Intermediate
alleneeealleneee

break-loop

Generate structured post-mortem reports from debugging sessions.

Community
Advanced
d-o-hubd-o-hub
11

github-workflows-caching-strategies

Optimize GitHub Actions caching strategies for Rust CI/CD workflows.

Community
Intermediate
wahidyankfwahidyankf
3

monitor-ci

Monitor Nx Cloud CI Attempts and apply self-healing fixes.

Community
Advanced