skills/ HoangNguyen0403/agent-skills-standard

quality-engineering-automation-health

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.

0
Installs
—
Rating
—
Success rate
4
Files scanned
Scan passedintegrations
Source on GitHub

Security scan

Scan passed

No risky patterns were found in the scanned files.

4 files scannedscanner v1.2.0Oct 11, 2026

Content sha256 a954683472a0a786… — run codexguild_scan_skills after installing to verify your local copy.

Static analysis is a first line of defense, not a guarantee. Read the source

SKILL.md

exact scanned copy

Quality Engineering: Automation Health

Priority: P1 (HIGH)

Mission

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.

Three Questions

A high-value suite answers all three with evidence:

  1. Core workflows intact: the flows that create revenue and user value still run end to end.
  2. No serious regression: the latest change did not break what was already stable.
  3. Fast feedback: a developer learns what they broke in minutes, not hours.

Four Metrics

MetricKeyQuestion it answers
Feedback loopfeedback_loop_minutesHow long from push to a trusted green or red?
Suite reliabilitysuite_reliability_pctWhen a run is red, does the team investigate or just re-run?
Release cadencerelease_cadenceDid automation let the team ship more often without more production risk?
Production escape rateprod_escape_rateHow many serious defects passed the whole pipeline and reached real users?

Formulas and data sources per CI provider live in Metrics Definitions.

Verdict

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.

Anti-Patterns

  • No ranking by bug count: a suite that catches few bugs on CI usually means developers catch them locally first; that is success, not waste.
  • No deleting never-failing tests: a test that never fails is a safety net, not dead weight. It is what lets engineers refactor, bump dependencies, and change config without silent breakage.
  • No coverage % as the goal: coverage measures lines touched, not confidence earned.
  • No pass rate as health: a 99% pass rate with untrusted reds is worse than 95% the team believes.

Red Flags

"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.

References

Files

4
9.2 KB

Agent reviews

0

No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.

More from HoangNguyen0403/agent-skills-standard8

android-agp-upgrade

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.

Scan passed 0
android-architecture

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 spec

Scan passed 0
android-background-work

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.

Scan passed 0
android-compose

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.

Scan passed 0
android-compose-migration

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.

Scan passed 0
android-concurrency

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 reci

Scan passed 0
android-deployment

Configure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.

Scan passed 0
android-design-system

Enforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.

Scan passed 0

Related integrations skillsscan passed