flaky-fix

Analyze and repair flaky tests using AST analysis and pattern matching.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the frustration and wasted time caused by unreliable, intermittently failing tests in software development, aiming to improve CI/CD stability.

Core Features & Use Cases

  • Automated Flaky Test Detection & Repair: Analyzes test code to identify common patterns leading to flakiness (timing, async, state, etc.) and suggests or applies fixes.
  • Pattern-Based Fixes: Leverages research on flaky test taxonomies to apply deterministic solutions like mocking time, proper async handling, and test isolation.
  • Use Case: A developer's CI pipeline is failing intermittently due to a specific test. They can use this Skill to analyze the test, identify the root cause (e.g., a race condition), and automatically refactor the test to be stable.

Quick Start

Use the flaky-fix skill to analyze and automatically repair the flaky test located at test/user_auth.test.ts.

Frequently Asked Questions about flaky-fix

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

FAQPage Schema
How do I automatically fix flaky tests caused by timing issues and race conditions?

You can automatically fix flaky tests by analyzing the test code to identify timing anti-patterns and applying deterministic repairs like mocking time and proper asynchronous handling.

Why does my CI/CD pipeline fail intermittently due to test order dependencies?

Intermittent CI/CD failures from test order dependencies occur when tests share state. This Skill analyzes code using AST analysis to identify these non-deterministic patterns and applies test isolation fixes.

How to repair unreliable tests that fail due to non-deterministic values and environment interactions?

To repair unreliable tests, the Skill utilizes pattern matching to detect non-deterministic values and environment interactions, then automatically refactors the test code to apply deterministic solutions.

What is the best way to handle flaky tests in software projects without manual debugging?

The best way to handle flaky tests without manual debugging is using automated pattern-based fixes that leverage flaky test taxonomies to refactor tests for stability and improve CI/CD reliability.

Can I use automated test repair for asynchronous operations in my test suite?

Yes, automated test repair can be used for asynchronous operations by analyzing the test code to identify improper async handling and applying deterministic fixes to resolve the flakiness.

When should I not use automated flaky test repair for my codebase?

You should not use automated flaky test repair when the root cause of test failure is an actual application bug rather than a test anti-pattern, as the AST analysis specifically targets test code non-determinism.