fix-flaky-test

Reproduce and resolve flaky tests by configuring environments, running tests, and analyzing results.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/sast-playground/aspire --skill fix-flaky-test-sast-playground
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-flaky-test
Source: https://github.com/sast-playground/aspire/tree/main/.github/skills/fix-flaky-test
Command: npx skills add https://github.com/sast-playground/aspire --skill fix-flaky-test-sast-playground

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the investigation, reproduction, and resolution of flaky tests, saving time and reducing frustration.

Core Features & Use Cases

  • Automated Test Reproduction: Reproduce flaky tests locally and on CI to identify the root cause.
  • Investigation Workflow: Provides a structured process for investigating and resolving flaky tests.
  • Two-Branch Workflow: Uses two branches to separate investigation and fix work.
  • Reproducible Results: Ensures consistent results across different environments.

Quick Start

Run the 'fix-flaky-test' skill with the test method name and issue URL.

Frequently Asked Questions about fix-flaky-test

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

FAQPage Schema
How do I automate the reproduction of flaky tests in my CI workflow?

To automate flaky test reproduction, you can execute scripts that configure the test environment, run the tests, and analyze the results. This structured workflow identifies the root cause by ensuring consistent reproduction locally and across CI environments.

What is the best way to investigate and fix flaky tests without disrupting my main branch?

The best way to investigate and fix flaky tests is by using a two-branch workflow. This approach separates your investigation process from the actual fix, ensuring that test reliability efforts do not disrupt your primary development branch.

Can I resolve test reliability issues locally before pushing to continuous integration?

Yes, you can resolve test reliability issues locally. The process requires local machine access to execute tests and analyze logs, allowing you to reproduce flaky behavior and verify the fix before integrating changes into your CI pipeline.

Do I need local machine access to reproduce flaky tests?

Yes, local machine access is required to reproduce flaky tests. The automated investigation process depends on local test execution and log analysis capabilities to configure the environment and accurately identify the root cause of the inconsistency.

Why does my test pass locally but fail in continuous integration environments?

Your test may pass locally but fail in CI due to environmental inconsistencies. Automating flaky test reproduction helps identify these root causes by executing scripts that configure the test environment and analyze results across different environments.