skills.rest
AZANIR
AZANIRCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

qa-flaky-detector

Analyze CI history to classify flaky tests into four failure patterns.

2|2|Updated Mar 7, 2026
Search Tags:#ci/cd#test automation#debugging#qa#flaky tests#test stability
One-click install
npx skills add https://github.com/AZANIR/qa-skills --skill qa-flaky-detector
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: qa-flaky-detector
Source: https://github.com/AZANIR/qa-skills/tree/main/.cursor/skills/qa-flaky-detector
Command: npx skills add https://github.com/AZANIR/qa-skills --skill qa-flaky-detector

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automatically identifies and classifies intermittent test failures (flakiness) in your CI/CD pipeline, providing actionable insights to improve test stability and reliability.

Core Features & Use Cases

  • Flaky Test Detection: Analyzes CI history to flag tests that pass and fail inconsistently.
  • Root Cause Classification: Categorizes flakiness into four common patterns: race conditions, shared state, time-dependency, and external dependencies.
  • Fix Suggestions: Offers specific, pattern-based recommendations to resolve flaky tests.
  • Use Case: Your CI runs are unreliable due to flaky tests. Use this Skill to pinpoint which tests are flaky, understand why they are failing intermittently, and get concrete steps to fix them, leading to more stable builds.

Quick Start

Analyze the CI history to find and classify flaky tests.

Frequently Asked Questions about qa-flaky-detector

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

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

To identify flaky tests in your CI/CD pipeline, analyze CI execution history and test data to flag tests that pass and fail inconsistently. This process automates detection by examining historical run data to pinpoint intermittent failures.

What are the common root causes of intermittent test failures?▼

Intermittent test failures are commonly caused by race conditions, shared state, time-dependency, and external dependencies. This Skill classifies flaky tests into these four distinct patterns to help pinpoint the exact root cause.

How do I fix flaky tests caused by race conditions and shared state?▼

To fix flaky tests caused by race conditions and shared state, use pattern-based fix suggestions provided after classifying the failure. The Skill offers specific recommendations to resolve each identified flakiness pattern.

Can I analyze test stability without integrating new dependencies?▼

Yes, you can analyze test stability without integrating new dependencies. This Skill operates independently without requiring any external dependencies to analyze CI history and classify flaky test patterns.

What is the best way to debug time-dependency issues in test automation?▼

The best way to debug time-dependency issues in test automation is to analyze CI execution history to classify the flakiness pattern. This Skill identifies time-dependency issues and provides concrete steps to fix them.

Related Skills

Explore More Software Engineering Skills→
rakhnianskii9rakhnianskii9

test-flakiness

Analyze CI run logs and test histories to detect flaky tests and maintain a registry.

Community
Advanced
arbazkhan971arbazkhan971
26

debug

Reproduce failing tests and runtime errors to prove root causes with file:line evidence.

Community
Advanced
CENKSSSCENKSSS

test-automation-strategy

Design test automation frameworks and integrate CI/CD pipelines.

Community
Advanced
robotijnrobotijn
3

concurrency-checker

Detect race conditions, deadlocks, and TOCTOU flaws across 7 programming languages.

Community
Advanced