flaky-hunter

Diagnose intermittent test failures by executing tests multiple times and analyzing flakiness causes.

746|130|Updated Jun 30, 2026
One-click install
npx skills add https://github.com/Archive228/loopkit --skill flaky-hunter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flaky-hunter
Source: https://github.com/Archive228/loopkit/tree/main/skills/flaky-hunter
Command: npx skills add https://github.com/Archive228/loopkit --skill flaky-hunter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps diagnose and fix tests that intermittently pass and fail, ensuring consistent CI pipeline reliability.

Core Features & Use Cases

  • Flaky Test Detection: Identifies tests that are flaky by running them multiple times.
  • Root Cause Analysis: Provides insights into common causes of flakiness, such as timing issues, asynchronous race conditions, and resource leaks.
  • Fix Recommendations: Offers guidance on how to address flakiness, including isolating tests, awaiting promises, mocking external factors, and handling resource leaks.

Quick Start

Run the flaky test with the 'flaky-hunter' skill to identify and fix flakiness issues.

Frequently Asked Questions about flaky-hunter

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

FAQPage Schema
How do I diagnose intermittent test failures in my CI pipeline?

You can resolve flaky tests by running them multiple times to detect inconsistent behavior, analyzing root causes like asynchronous race conditions and resource leaks, and applying recommended fixes such as isolating tests, awaiting promises, and mocking external factors.

What causes flaky tests in continuous integration pipelines?

Intermittent CI failures are often caused by asynchronous race conditions and resource leaks; this Skill detects them by executing tests multiple times and recommending fixes like awaiting promises, mocking external factors, and handling resource leaks.

Do I need to understand asynchronous programming to fix flaky tests?

Yes, understanding asynchronous programming and resource management is required to fully diagnose intermittent test failures and implement reliable fixes for asynchronous race conditions and resource leaks.

What is the best way to isolate a flaky test in a test automation suite?

The best way to isolate a flaky test is to execute it multiple times to confirm its inconsistent behavior, then analyze root causes like asynchronous race conditions and resource leaks to apply targeted fixes such as mocking external factors.

How do I fix test reliability issues caused by resource leaks?

To fix test reliability issues caused by resource leaks, run the tests multiple times to detect the intermittent failures, then apply recommended handling techniques like isolating tests and mocking external factors to resolve the resource leaks.