triage-ci-flake

Name: triage-ci-flake
Availability: InStock
Author: Yoked

Reproduce and debug flaky CI test failures locally.

Updated Feb 28, 2026

Search Tags:#vitest #testing #debugging #flaky tests #playwright #ci

Ready to run

npx skills add https://github.com/Getyokedapp/payload-cms --skill triage-ci-flake

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: triage-ci-flake
Source: https://github.com/Getyokedapp/payload-cms/tree/main/.claude/skills/triage-ci-flake
Command: npx skills add https://github.com/Getyokedapp/payload-cms --skill triage-ci-flake

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a systematic workflow to diagnose and fix intermittent or flaky test failures that occur in Continuous Integration (CI) environments, especially when tests pass locally.

Core Features & Use Cases

Reproduce Failures: Guides through precise steps to reproduce CI test failures locally, differentiating between development and bundled code environments.
Systematic Debugging: Offers a structured approach to isolate the root cause of flaky tests, covering race conditions, test pollution, and timing issues.
Use Case: A pull request fails in CI due to an intermittent E2E test timeout. This Skill helps you reproduce the failure locally, identify if it's a bundling issue, and then debug the specific test to find and fix the root cause.

Quick Start

Use the triage-ci-flake skill to reproduce and debug a failing CI test for the 'auth' suite.

Frequently Asked Questions about triage-ci-flake

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

FAQPage Schema

How do I reproduce flaky CI test failures locally when tests pass on my machine?▼

To reproduce flaky CI test failures locally, you must execute a mandatory reproduction workflow that differentiates between development and bundled code environments. This structured approach isolates timing, bundling, or environment differences causing the intermittent CI failures.

Why do my Vitest or Playwright E2E tests time out in CI but pass locally?▼

E2E tests time out in CI due to race conditions, test pollution, or bundling differences between local development and bundled code. Systematically debugging these flaky test failures involves reproducing the CI environment locally to isolate the specific timing issue.

What is the best way to debug intermittent test failures caused by bundling differences?▼

The best way to debug intermittent test failures from bundling differences is following a systematic workflow that isolates issues by running specific command executions. This process distinguishes between local development and bundled code execution to find the root cause.

How do I isolate race conditions and test pollution in a CI environment?▼

You isolate race conditions and test pollution in a CI environment by systematically reproducing the flaky failures locally. This debugging workflow guides you through specific command executions to identify timing and environment differences before proposing fixes.

Does this flaky test debugging workflow work with both Vitest and Playwright?▼

Yes, this flaky test debugging workflow supports both Vitest and Playwright. It systematically reproduces and debugs intermittent test failures across these testing frameworks, differentiating between local development and bundled code execution environments to isolate root causes.