mobile-release-readiness-audit

What problem does it solve?

Audits mobile apps for pre-release readiness across iOS (Swift/SwiftUI/UIKit), Android (Kotlin/Jetpack Compose), Flutter (Dart), and React Native. Produces a ship / ship-with-caveats / block verdict backed by findings in six layers — privacy & permissions, accessibility, localization, crash-prone code, store metadata, and release-build hygiene. This audit engine helps release managers catch rejection-prone issues on the final submission day and provide a structured report to stakeholders.

Core Features & Use Cases

This skill is a pre-ship audit engine for mobile apps. It is NOT a code formatter, NOT a test runner, and NOT a generic linter. It inspects a mobile codebase the way a senior mobile release manager would on the last day before submission — catching the specific, rejection-prone, user-visible failure modes that generic LLM suggestions miss.

When activated, your job is to:

• Identify the platform(s) in play — iOS native, Android native, Flutter, React Native, or hybrid.
• Run the six-layer audit below. Do not skip layers even if one looks clean.
• Assign each layer a verdict: PASS, WARN, or FAIL, with evidence (file:line or snippet).
• Produce an overall release verdict using the decision rules at the end.
• Output the structured report in the format shown in the final section.

Operate like a reviewer, not a cheerleader. If you cannot determine something from the material given, say UNKNOWN — need X rather than guessing. A false PASS is worse than a WARN.

Quick Start

Audit a mobile app repository to generate a six-layer release readiness report.