Measures whether an automation suite builds release confidence via feedback-loop length, suite reliability, release cadence, and production escape rate, and emits a release_confidence verdict. Use when judging suite value, ROI, or pre-release trust; not for writing or healing tests.
中文简介正在准备中。当前显示原文说明。
实测评分 未实测
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Automation exists to reduce ambiguity at release time, not to catch every bug. Finding bugs is testing's job; building confidence is automation's. Judge a suite by whether the team can deploy on Friday afternoon without fear.
A high-value suite answers all three with evidence:
| Metric | Key | Question it answers |
|---|---|---|
| Feedback loop | feedback_loop_minutes | How long from push to a trusted green or red? |
| Suite reliability | suite_reliability_pct | When a run is red, does the team investigate or just re-run? |
| Release cadence | release_cadence | Did automation let the team ship more often without more production risk? |
| Production escape rate | prod_escape_rate | How many serious defects passed the whole pipeline and reached real users? |
Formulas and data sources per CI provider live in Metrics Definitions.
release_confidence: high | medium | low
high: all three questions answered yes with evidence; reliability at or above the team threshold; escape rate at or below baseline; feedback loop within target.medium: one question lacks evidence, or reliability or feedback loop misses target while escapes stay at baseline.low: any question answered no, a red run is not trusted, or escape rate rose after the last release.Report with Confidence Report Template; feed release_confidence into test-loop, uat-signoff, and deploy-release handoffs.
"this test never fails, delete it" · "just re-run it, it's probably flaky" · "we found zero bugs so automation isn't paying off" · "coverage is 90%, we're safe". Each swaps a confidence question for a vanity number; re-frame with the Three Questions before acting.
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
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.
中文简介正在准备中。当前显示原文说明。