fix-flaky-test

Diagnose and resolve flaky tests in the FluidFramework repository.

Updated Jan 7, 2026
One-click install
npx skills add https://github.com/tylerbutler/repo-overlays --skill fix-flaky-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-flaky-test
Source: https://github.com/tylerbutler/repo-overlays/tree/main/tylerbutler/FluidFramework/jikim-superskills/.claude/skills/fix-flaky-test
Command: npx skills add https://github.com/tylerbutler/repo-overlays --skill fix-flaky-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers identify and fix unreliable tests that intermittently fail, improving the stability and trustworthiness of the CI/CD pipeline.

Core Features & Use Cases

  • Automated Test Analysis: Diagnoses common causes of flaky tests, such as race conditions, timer dependencies, and shared state issues.
  • Targeted Fixes: Provides specific code examples and strategies for resolving identified test instability.
  • Use Case: A developer is facing a test that passes sometimes and fails others. They can use this Skill to analyze the test's code, identify potential race conditions, and receive a corrected code snippet to ensure consistent test results.

Quick Start

Use the fix-flaky-test skill to diagnose and fix the flaky test named 'user login should succeed'.

Frequently Asked Questions about fix-flaky-test

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

FAQPage Schema
How do I fix flaky tests caused by race conditions in TypeScript?

Fix flaky tests by analyzing test code for race conditions, timer dependencies, and shared state issues. This skill diagnoses non-deterministic ordering in TypeScript and Mocha, providing specific code fixes and verification steps to ensure consistent test stability.

What are common causes of intermittent test failures in CI/CD pipelines?

Intermittent test failures in CI/CD pipelines are commonly caused by race conditions, timer dependencies, shared state issues, and non-deterministic ordering. Analyzing asynchronous JavaScript patterns helps identify these instabilities to provide targeted code corrections.

How do I resolve non-deterministic test ordering in Mocha?

Resolve non-deterministic Mocha test ordering by analyzing the test code for shared state and asynchronous JavaScript patterns. This skill diagnoses the instability and provides specific code fixes to ensure tests run consistently regardless of execution order.

Can I use this to debug timer dependencies in asynchronous JavaScript tests?

Yes, you can debug timer dependencies in asynchronous JavaScript tests. The skill analyzes test code for timer-related instabilities and provides specific code fixes and verification steps to ensure test stability.

Why does my test pass locally but fail intermittently in CI/CD?

Tests passing locally but failing in CI/CD often stem from race conditions, shared state, or non-deterministic ordering under load. Analyzing the test code for these asynchronous JavaScript patterns yields specific fixes to stabilize the CI/CD pipeline.

What's the best way to diagnose unstable FluidFramework repository tests?

Diagnose unstable FluidFramework repository tests by analyzing the TypeScript and Mocha test code for race conditions and shared state. The skill provides specific code fixes and verification steps to ensure long-term test stability.