test-flakiness

Detect flaky tests in CI logs from GitHub Actions, Unity, Godot, or Unreal.

14|1|Updated Apr 12, 2026

Search Tags:#automation #git #qa #ci #flaky-tests #test-analysis #regression-suite

Ready to run

npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill test-flakiness-euraika-labs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-flakiness
Source: https://github.com/Euraika-Labs/Codex-Code-Game-Studios/tree/main/.agents/skills/test-flakiness
Command: npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill test-flakiness-euraika-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Flaky tests pass intermittently without code changes, causing missed failures and eroding confidence in CI pipelines. This skill detects such non‑deterministic tests and helps teams address them before release.

Core Features & Use Cases

Log Analysis: Scans CI run logs or test result artifacts from GitHub Actions, Unity, Godot, and Unreal pipelines.
Flakiness Detection: Aggregates pass rates per test across multiple runs, classifies flakiness levels, and suggests likely causes.
Actionable Recommendations: Proposes quarantine, fixes, or monitoring actions and updates the regression‑suite documentation.
Report Generation: Creates a concise flakiness summary and an optional detailed QA report for project leads.
Use Case Example: During the polish phase of a game project, run this skill to ensure the test suite is stable before the release gate.

Quick Start

Run the test-flakiness skill to scan CI logs and update the regression suite.

Frequently Asked Questions about test-flakiness

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

FAQPage Schema

How do I detect flaky tests in my CI pipeline?▼

Detect flaky tests in CI pipelines by analyzing test result logs from multiple runs to aggregate pass rates, classify flakiness levels, and identify intermittent failures. This process scans logs to find non-deterministic tests that pass intermittently without code changes.

What causes intermittent test failures in GitHub Actions?▼

Intermittent test failures in GitHub Actions are caused by non-deterministic tests that pass or fail without code changes. Analyzing CI run logs across multiple runs aggregates pass rates and classifies flakiness levels to pinpoint these unstable tests.

Can I scan Unity or Unreal project logs for flaky tests?▼

Yes, you can scan Unity, Godot, or Unreal project logs for flaky tests. The analysis works directly with test result artifacts from these game engine pipelines to identify intermittent failures during the polish phase.

How do I quarantine flaky tests in a regression suite?▼

Quarantine flaky tests in a regression suite by analyzing CI run logs to classify flakiness levels and recommend specific actions. The process proposes quarantine, fixes, or monitoring and updates the regression suite documentation automatically.

How do I generate a QA report for unstable tests?▼

Generate a QA report for unstable tests by aggregating pass rates across multiple CI runs and classifying flakiness levels. This creates a concise flakiness summary and an optional detailed QA report for project leads.

When should I analyze test flakiness before a release?▼

Analyze test flakiness before a release during the polish phase of a project. Running log analysis on multiple CI runs at this stage ensures the test suite is stable and identifies intermittent failures before the release gate.