mobile-release-readiness-audit

Audit mobile app repositories across iOS, Android, Flutter, and React Native for release readiness.

17|29|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/lucifertrj/skills-based-app --skill mobile-release-readiness-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mobile-release-readiness-audit
Source: https://github.com/lucifertrj/skills-based-app/tree/main/community/Richik_Chaudhuri%281BM23CD050%29/mobile-release-readiness-audit
Command: npx skills add https://github.com/lucifertrj/skills-based-app --skill mobile-release-readiness-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about mobile-release-readiness-audit

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

FAQPage Schema
How do I audit my mobile app for store release readiness before submission?▼

You can audit mobile app release readiness by running a six-layer check across privacy, accessibility, localization, crash-prone code, store metadata, and build hygiene to generate evidence-backed PASS/WARN/FAIL verdicts.

Does the mobile release audit support React Native and Flutter hybrid projects?▼

Yes, the release audit supports React Native and Flutter hybrid projects alongside native iOS and Android, automatically identifying platforms in play and applying per-layer readiness checks to each.

What does a pre-ship mobile app accessibility and privacy audit check for?▼

A pre-ship accessibility and privacy audit checks mobile codebases for rejection-prone issues like improper permissions, missing localization, crash-prone code, and incomplete store metadata before final submission.

How do I generate a structured release readiness report for app store stakeholders?▼

Generate a structured release readiness report by scanning your mobile repository to produce an overall ship or block verdict with file-level evidence across six audit layers suitable for stakeholder submission.

What is the difference between a generic linter and a pre-ship mobile release audit?▼

A pre-ship mobile release audit inspects codebases for user-visible rejection risks like store metadata and privacy compliance, whereas a generic linter focuses on code formatting and style without producing release verdicts.

Why does my mobile release audit return UNKNOWN instead of a PASS verdict?▼

An UNKNOWN verdict appears when the audit cannot determine readiness from the provided material, enforcing strict evidence-backed checks where a false PASS is worse than a WARN to prevent store rejection.