flaky-detect

Analyze CI history and code patterns to identify flaky tests.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/robit-man/transcribe-cli --skill flaky-detect-robit-man
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flaky-detect
Source: https://github.com/robit-man/transcribe-cli/tree/main/.claude/skills/flaky-detect
Command: npx skills add https://github.com/robit-man/transcribe-cli --skill flaky-detect-robit-man

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill identifies and helps to resolve flaky tests – those that pass and fail intermittently – which undermine CI/CD pipeline stability and developer productivity.

Core Features & Use Cases

  • CI History Analysis: Detects inconsistent test results across multiple CI runs.
  • Code Pattern Scanning: Identifies common code anti-patterns that lead to flakiness.
  • Re-run Analysis: Facilitates systematic re-running of tests to confirm flakiness.
  • Use Case: When your CI pipeline is frequently broken by tests that pass on retry, this Skill can pinpoint the exact tests causing the instability and suggest root causes like timing issues or environment dependencies.

Quick Start

Analyze CI history for flaky test patterns over the last 30 days.

Frequently Asked Questions about flaky-detect

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, you can analyze your CI history to detect inconsistent test results across multiple runs. This approach pinpoints tests that pass and fail intermittently, exposing specific tests causing pipeline instability and reducing developer productivity.

Why do intermittent test failures occur and how can I find the root cause?

Intermittent test failures often stem from timing issues or environment dependencies. You can find the root cause by scanning your code for common anti-patterns that lead to flakiness, which helps address the underlying issues causing unreliable test results.

What is the best way to confirm if a test is actually flaky?

The best way to confirm if a test is flaky is by performing a systematic re-run analysis. Facilitating systematic re-running of tests validates whether the intermittent failures are genuine flakiness rather than consistent code defects.

Can I use Python scripts to detect test reliability issues from historical CI data?

Yes, you can use Python scripts for historical data parsing to detect test reliability issues. The scripts parse CI history, perform pattern matching against known anti-patterns, and aggregate results to highlight unreliable tests.

Does this flaky test detection approach work without external dependencies?

Yes, this approach to flaky test detection works without external dependencies. It operates autonomously using internal scripts and references to parse CI history and scan code for anti-patterns, requiring no additional packages.