Failure taxonomy and allowed/forbidden repairs for a failing E2E test. Use when a Playwright/Maestro/Detox/XCUITest/Espresso/Appium test fails and you must decide whether to repair the test or route to a real bug.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
SELECTOR_DRIFT (id/locator changed) · TIMING_SYNC (race/wait, no state change) · DATA_ENV (fixture/seed/env stale) · INFRA (network/runner/flake) · REAL_REGRESSION (product behavior actually changed).
Classify from evidence: trace/screenshot/DOM diff supports a drift/timing/data explanation, or the product diff shows an intentional behavior change (REAL_REGRESSION).
Move the locator up the selector ladder (e.g., getByRole if the ID changed); replace a sleep with an explicit state wait; fix a stale fixture/seed; retry only for INFRA.
Never weaken an assertion. Never add test.skip/fixme; a test that must stop gating goes to quarantine per quality-engineering-flaky-triage with a ticket + expiry, and keeps running. Never widen a matcher. Never inflate a timeout by more than 2x. Never blind --update-snapshots. Never catch-and-continue. Never touch production code — that is REAL_REGRESSION, not a heal.
HEALED (repair verified by 3 consecutive green reruns, ASSERTION_DELTA: none) · REAL_BUG_DO_NOT_HEAL (route to dev-fix) · QUARANTINE_CANDIDATE (flaky, route to flaky-triage) · BLOCKED (no evidence artifact, or no stable locator target: route to specialist-testid-inserter).
"the assertion was too strict anyway" · "the product changed so update the expected value" · "just add retries so it goes green" — do not heal with these rationalizations. All three are REAL_BUG_DO_NOT_HEAL or QUARANTINE_CANDIDATE in disguise, never HEALED.
QUARANTINE_CANDIDATEREAL_REGRESSIONまだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.
日本語の概要は準備中です。原文の説明を表示しています。
Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their specific skills.
日本語の概要は準備中です。原文の説明を表示しています。
Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.
日本語の概要は準備中です。原文の説明を表示しています。
Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.
日本語の概要は準備中です。原文の説明を表示しています。
Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.
日本語の概要は準備中です。原文の説明を表示しています。
Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test recipes to their specific skills.
日本語の概要は準備中です。原文の説明を表示しています。