Skip to content
Back to skills

Prep Release

ASecurity

Pre-release audit for a React Native app. Use when the user is about to submit to the App Store or Play Store, cut a release, or asks for a release checklist run.

  • 3 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 6, 2026
ai-agentsreactgitapibackend

Works with

  • api

Security analysis

A100/100

Scanned September 22, 2026

npx -y skills add AnilBurcu/claude-code-react-native --skill prep-release --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Prep Release?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Prep Release
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/anilburcu-prep-release/badge)](https://www.skillsdirectory.com/skills/anilburcu-prep-release)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: prep-release
description: Pre-release audit for a React Native app. Use when the user is about to submit to the App Store or Play Store, cut a release, or asks for a release checklist run.
argument-hint: "[ios|android|both]"
disable-model-invocation: true
---

Run a pre-release audit for `$ARGUMENTS` (default: both platforms). Verify in the actual project files; never assume. Output a pass/fail table with evidence, so the user can fix failures and rerun.

Check, with the eas-release skill as the rulebook:

1. **Versioning**: user-facing version bumped since the last release tag; build numbers set to auto-increment or manually bumped; git tag plan stated.
2. **OTA fence**: runtime version policy present; if any native dependency or config plugin changed since the last store build, flag that this release MUST be a store build and OTA publishing to old channels is forbidden until it ships.
3. **Permissions honesty**: cross-check declared permissions and usage strings (Info.plist keys, Android permissions) against what the code actually imports. Camera/mic/location/notification strings present where used, and no leftover permissions from removed features, which reviewers flag.
4. **Secrets scan**: grep the source and app config for things that must not ship: private API keys, service-role or server keys, live payment secrets, hardcoded backend admin URLs. Public/publishable keys are fine; call out anything ambiguous.
5. **Store hygiene**: account deletion path exists if accounts exist; restore purchases reachable if IAP exists; sign-in options meet platform rules; privacy labels and data safety answers match the SDK list (list the SDKs that collect data so the user can compare).
6. **Config sanity**: production build profile points at production backend; no debug flags, staging URLs or test paywalls behind release config; app icon and splash present for both platforms.
7. **Quality gates**: typecheck, lint and tests pass; if there is a preview/QA build lane, confirm the release candidate went through it.
8. **Android native alignment**: when a build artifact is at hand, verify 16 KB page alignment of native libraries (`zipalign -c -P 16 -v 4` on an APK built from the bundle); Play rejects unaligned `.so` files for apps targeting Android 15+. Without an artifact, list native dependencies whose last release predates the requirement as warnings.

Rules of engagement: read-only plus running the project's own check commands. Findings come back as blocker vs warning, each with file evidence. End with a plain verdict: ready to submit, or the ordered list of what blocks it.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.