flaky-hunter

스타2

포크0

업데이트2026년 7월 12일 12:09

Diagnose and fix tests that pass sometimes and fail other times. Use when CI is red intermittently.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

YaoYinYing

YaoYinYing/REvoDesign

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Flaky Test Hunter

Run the suspect test 20x in a loop first — confirm it's actually flaky, not just broken. Common causes, in order of likelihood:

Time/order — depends on test execution order or shared mutable state. Isolate it; run alone.
Async race — asserting before a promise/refetch resolves. Await the actual condition, not a sleep.
Real network/clock/random — mock them. Freeze time, seed RNG, stub the call.
Resource leak — a prior test left a connection/file/port open. Fix the cause, not the symptom. retry(3) on a flaky test hides a real race that will bite in production. Quarantine only as a last resort, with a ticket.

이 저장소의 다른 Skills

같은 저장소

adversarial-verify

YaoYinYing/REvoDesign

Review a diff against the goal spec assuming the code is BROKEN. The reviewer that lives in the maker's head always agrees with itself — this pulls review into a hostile, separate pass. Invoke after every code change before marking work done.

2026-07-122

authz-check

YaoYinYing/REvoDesign

Verify that an endpoint checks ownership, not just authentication. Use on any handler that reads or mutates user data.

2026-07-122

bisect-regression

YaoYinYing/REvoDesign

Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.

2026-07-122

changelog-from-diff

YaoYinYing/REvoDesign

Turn a set of commits or a diff into a clean, user-facing changelog entry. Use before a release or PR description.

2026-07-122

clean-commits

YaoYinYing/REvoDesign

Turn messy WIP into clean, atomic commits with messages that explain why. Use before opening a PR.

2026-07-122

context-budget

YaoYinYing/REvoDesign

Keep the agent's context lean so accuracy doesn't collapse. Use on long sessions, big files, or when the agent starts hallucinating.

2026-07-122

name	flaky-hunter
description	Diagnose and fix tests that pass sometimes and fail other times. Use when CI is red intermittently.
when_to_use	intermittent CI failure, "passes locally fails in CI", a flaky test

Flaky Test Hunter

Run the suspect test 20x in a loop first — confirm it's actually flaky, not just broken. Common causes, in order of likelihood:

Time/order — depends on test execution order or shared mutable state. Isolate it; run alone.
Async race — asserting before a promise/refetch resolves. Await the actual condition, not a sleep.
Real network/clock/random — mock them. Freeze time, seed RNG, stub the call.
Resource leak — a prior test left a connection/file/port open. Fix the cause, not the symptom. retry(3) on a flaky test hides a real race that will bite in production. Quarantine only as a last resort, with a ticket.