android-play-quality-prelaunch-readiness

Assess Android app readiness for Google Play staged rollout from pre-launch reports and QA checks.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/joshka0/foxctl --skill android-play-quality-prelaunch-readiness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: android-play-quality-prelaunch-readiness
Source: https://github.com/joshka0/foxctl/tree/main/configs/skills-external/android-play-quality-prelaunch-readiness
Command: npx skills add https://github.com/joshka0/foxctl --skill android-play-quality-prelaunch-readiness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you decide whether an Android build is stable enough for Play testing and production by evaluating real crash, ANR, and onboarding risk beyond upload validation.

Core Features & Use Cases

  • Pre-launch report review: Flags critical issues found in Google Play pre-launch reports (crashes, ANRs, startup/auth failures, performance, device coverage, and unsupported device problems).
  • Manual QA readiness matrix: Provides a comprehensive checklist for fresh install, upgrades, auth, network edge cases, permissions, deep links, purchases, AI/reporting flow, and device/UX constraints (low-end, large font, dark mode, rotation).
  • Rollout monitoring & stop criteria: Defines what to monitor during staged rollout (crash-free sessions, auth errors, billing events, AI moderation/report metrics) and how to pause or rollback.

Quick Start

Use this skill to assess your Play build’s readiness by reviewing the pre-launch report results, running the critical QA matrix on representative devices, and producing a quality verdict with required fixes.

Frequently Asked Questions about android-play-quality-prelaunch-readiness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check Android app readiness for a Google Play staged rollout?

Evaluate Android app readiness by reviewing the Play pre-launch report for crashes and ANRs, completing a manual critical QA matrix, and defining rollout monitoring criteria to output a structured quality verdict and fix plan.

What is a crash gating checklist for an Android release?

A crash gating checklist assesses real-device crash, ANR, startup, and auth risks beyond standard upload validation to ensure the build is stable enough for Play testing and production tracks.

How do I review a Google Play pre-launch report for ANR and crash risks?

Review a Play pre-launch report by flagging critical crashes, ANRs, startup or auth failures, performance issues, and unsupported device problems to assess onboarding risk and determine production release stability.

Does Android release gating require manual QA on real devices?

Yes, Android release gating requires manual QA on real devices to verify fresh installs, upgrades, auth, network edge cases, permissions, deep links, and UX constraints like low-end performance, large fonts, and dark mode.

What should I monitor during an Android staged rollout to decide whether to pause?

During an Android staged rollout, monitor crash-free sessions, auth errors, billing events, and AI moderation metrics against predefined stop criteria to determine whether to pause or rollback the release.

Can I use this release gating process for Expo native production-mode builds?

Yes, the release gating process applies to Expo-native production-mode verification and targeted regression testing for target SDK changes, ensuring comprehensive real-device QA coverage before Play publication.