test-fixer

Diagnose flaky Hex1b UI tests and apply remediation patterns.

173|17|Updated Dec 6, 2025

Search Tags:#automation #flaky-tests #UI-testing #Hex1b #test-fixer #WaitUntil

Ready to run

npx skills add https://github.com/mitchdenny/hex1b --skill test-fixer-mitchdenny

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-fixer
Source: https://github.com/mitchdenny/hex1b/tree/main/.github/skills/test-fixer
Command: npx skills add https://github.com/mitchdenny/hex1b --skill test-fixer-mitchdenny

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides guidelines for AI agents to diagnose and fix flaky tests in the Hex1b TUI library test suite. These tests use Hex1bTerminalInputSequenceBuilder to simulate user interactions with terminal applications.

Core Features & Use Cases

Standardized diagnostic workflows for flaky tests in Hex1b
Common remediation patterns such as adding WaitUntil after state-changing actions, ensuring proper render sequencing, replacing Task.Delay with TaskCompletionSource, and avoiding Task.WhenAny race conditions
Guidance for tackling patterns like Missing WaitUntil, Race with Ctrl+C, Test Interference, and Platform-specific failures across the test suite

Quick Start

Use this skill to guide AI agents in diagnosing flaky Hex1b UI tests and generating concrete, repeatable fixes.

Frequently Asked Questions about test-fixer

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

FAQPage Schema

How do I fix flaky UI tests that simulate terminal interactions?▼

Diagnosing flaky terminal UI tests involves identifying Missing WaitUntil conditions, Task.WhenAny race conditions, Task.Delay timing gaps, and test interference patterns to apply targeted remediation strategies.

What causes flaky TUI library tests to fail intermittently?▼

Flaky TUI tests usually stem from missing WaitUntil synchronization after state changes, Task.Delay timing dependencies, Task.WhenAny race conditions, and test interference across the terminal test suite.

How do I diagnose race conditions in terminal UI test sequences?▼

Diagnose terminal UI test race conditions by identifying Task.WhenAny races and improper render sequencing, then replace Task.Delay with TaskCompletionSource to synchronize state changes deterministically.

Does this flaky test remediation guidance work for Hex1b terminal input sequences?▼

Yes, this flaky test remediation guidance specifically targets the Hex1b test suite using Hex1bTerminalInputSequenceBuilder, addressing platform-specific failures and terminal interaction timing pitfalls.

Why do my terminal UI tests fail when simulating Ctrl+C interactions?▼

Terminal UI tests simulating Ctrl+C often fail due to race conditions during cancellation handling; inserting WaitUntil and replacing Task.Delay with TaskCompletionSource ensures proper render sequencing and stable state transitions.