skills.rest
zinohome
zinohomeCOMMUNITY
Explore all skills by this author →
GitHub

flaky-test-detective

Diagnose flaky test patterns and run detection scripts for intermittent failures.

1|Updated Nov 6, 2025
Search Tags:#automation#testing#ci/cd#debugging#flaky tests#test stability
One-click install
npx skills add https://github.com/zinohome/CozyChat --skill flaky-test-detective
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: flaky-test-detective
Source: https://github.com/zinohome/CozyChat/tree/main/.claude/skills/flaky-test-detective
Command: npx skills add https://github.com/zinohome/CozyChat --skill flaky-test-detective

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill systematically diagnoses and fixes flaky tests, which are tests that intermittently pass and fail without code changes, leading to unreliable CI/CD pipelines and wasted developer time.

Core Features & Use Cases

  • Root Cause Analysis: Identifies common flaky test patterns like timing issues, shared state, randomness, and network dependencies.
  • Stabilization Strategies: Provides concrete solutions and best practices to make tests deterministic and reliable.
  • Automated Detection: Includes a script to run tests multiple times and report flaky tests.
  • Use Case: A developer is experiencing intermittent failures in their test suite. They can use this Skill to pinpoint the exact tests that are flaky, understand why they are failing (e.g., a race condition), and apply the recommended fixes to achieve stable test results.

Quick Start

Run the flaky test detection script to identify unstable tests in your project.

Frequently Asked Questions about flaky-test-detective

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

FAQPage Schema
How do I find flaky tests in my CI/CD pipeline?▼

You can find flaky tests in your CI/CD pipeline using an automated detection script that runs the suite multiple times to identify and report intermittent failures without code changes.

What causes intermittent test failures without code changes?▼

Intermittent test failures without code changes are typically caused by common flaky test patterns including timing issues, shared state, randomness, and network dependencies.

How do I fix race conditions and timing issues in automated tests?▼

Fix race conditions and timing issues in automated tests by diagnosing the root cause and applying concrete stabilization strategies to make test execution deterministic and reliable.

Do I need a specific testing framework to diagnose test stability issues?▼

Diagnosing test stability issues requires understanding of testing frameworks and CI/CD pipelines, but is not restricted to a specific platform to detect shared state and network dependencies.

What is the best way to stabilize an unreliable test suite?▼

The best way to stabilize an unreliable test suite is to pinpoint exact flaky tests, understand why they fail, and apply recommended fixes like resolving shared state or network dependency issues.

Related Skills

Explore More Software Engineering Skills→
HomericIntelligenceHomericIntelligence
18

extract-test-failures

Parse test execution logs to identify and categorize failures by type.

Official
Intermediate
manastalukdarmanastalukdar
1

pipeline-monitor

Analyze CI/CD pipeline build success rates, flaky tests, and duration trends.

Community
Advanced
evstackevstack
4

evolve-debugger

Record and replay blockchain execution traces for time-travel debugging.

Official
Advanced
RambleRainbowRambleRainbow

swift-protocol-di-testing

Abstract external Swift dependencies behind protocols for deterministic testing.

Community
Intermediate