skills.rest
sumilee-pcu
sumilee-pcuCOMMUNITY
Explore all skills by this author →
GitHub

test-flakiness

Detect non-deterministic test failures by analyzing CI logs and test artifacts.

Updated Apr 15, 2026
Search Tags:#automation#testing#debugging#ci-cd#quality-assurance#flakiness
One-click install
npx skills add https://github.com/sumilee-pcu/game2026 --skill test-flakiness-sumilee-pcu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-flakiness
Source: https://github.com/sumilee-pcu/game2026/tree/main/.claude/skills/test-flakiness
Command: npx skills add https://github.com/sumilee-pcu/game2026 --skill test-flakiness-sumilee-pcu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the frustration of non-deterministic test failures that erode trust in your CI/CD pipeline by identifying, categorizing, and managing flaky tests.

Core Features & Use Cases

  • Automated Detection: Parses CI logs and test results to identify tests that fail intermittently without code changes.
  • Root Cause Analysis: Classifies flakiness into categories like timing issues, order dependency, or resource leaks to guide developers toward the correct fix.
  • Registry Management: Maintains a quarantine list in your regression suite to ensure CI remains green while fixes are prioritized.

Quick Start

Run the test-flakiness skill in scan mode to analyze all available CI logs and generate a report on identified flaky tests.

Frequently Asked Questions about test-flakiness

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

FAQPage Schema
How do I identify flaky tests in my CI pipeline?▼

Flaky tests are detected by parsing CI log history and test result artifacts to find non-deterministic failures. This skill automates that detection process by running a scan across available logs and generating a report of intermittently failing tests.

What causes non-deterministic test failures in continuous integration?▼

Non-deterministic test failures are typically caused by timing issues, race conditions, order dependency, and environmental resource leaks. This skill classifies flakiness into these categories to guide developers toward the correct remediation fix.

How do I quarantine flaky tests to keep my CI pipeline green?▼

To quarantine flaky tests, maintain a registry list within your project regression suite. This skill facilitates automated quarantine workflows and remediation tracking to ensure CI remains green while fixes are prioritized.

Can I analyze CI logs to find race conditions in my regression suite?▼

Yes, you can analyze CI logs and test result artifacts to find race conditions within your regression suite. The skill supports diagnostic classification of flakiness causes including timing issues, race conditions, and environmental dependencies.

What's the best way to track remediation for quarantined tests?▼

Track remediation for quarantined tests by utilizing a quarantine list maintained within your regression suite. This skill provides remediation tracking alongside automated quarantine workflows to manage fixes for identified flaky tests.

Related Skills

Explore More Software Engineering Skills→
Euraika-LabsEuraika-Labs
14

test-flakiness

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

Official
Advanced
jmaglyjmagly
175

flaky-detect

Analyze CI history and test execution patterns to identify flaky tests.

Community
Advanced
hopeoverturehopeoverture
6

github-actions-ci-workflow

Generate GitHub Actions CI/CD workflows for web apps with lint, test, build, and deploy pipelines.

Community
Advanced
obraobra
269.6k

condition-based-waiting

Replace arbitrary timeouts with condition polling for asynchronous tests.

Community
Intermediate