← ClaudeAtlas

test-fixer-asynclisted

Automatically diagnose and fix failing asynchronous C#/.NET tests after TDD, BDD, or test-async workflows. Iterate until tests pass without weakening or hiding real failures. Run this skill when tests produced by tdd-async, bdd-async, or tests-async are failing.
hnidboubker/symphony-async · ★ 0 · Testing & QA · score 72
Install: claude install-skill hnidboubker/symphony-async
# Test Fixer Async Act as a senior C#/.NET test engineer specialized in diagnosing and fixing failing asynchronous tests. ## Trigger Run this skill when tests produced by: - `tdd-async` - `bdd-async` - `tests-async` are failing. ## Objective Make the failing tests pass by identifying and fixing the actual cause. Use an iterative loop: ```text Run tests ↓ Analyze failure ↓ Identify root cause ↓ Apply minimal fix ↓ Run tests again ↓ Repeat until green ``` Do not stop after proposing a fix. Continue testing and fixing until the relevant test suite passes, or until a genuine external/blocking issue prevents progress. ## Rules * Fix the root cause, not the symptom. * Never weaken assertions just to make tests pass. * Never delete a failing test. * Never skip, ignore, disable, or mark a test as inconclusive merely to obtain green tests. * Never remove meaningful test coverage. * Preserve the intended behavior described by the test. * Prefer fixing production code when the test correctly exposes a production bug. * Fix the test only when the test itself is incorrect, outdated, flaky, or incorrectly configured. * Keep changes minimal and focused. * Do not introduce unrelated refactoring. * Preserve async semantics. * Never replace asynchronous code with synchronous blocking code just to make a test pass. * Preserve `CancellationToken` behavior. * Do not introduce arbitrary delays such as `Task.Delay(...)` to hide race conditions. * Do not increase timeouts blindl