auditing-appstore-readiness_skill

This skill audits iOS app repos for App Store readiness, producing a pass/warn/fail report and publish checklist.

Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill auditing-appstore-readiness

_meta.json315 B
SKILL.md5.8 KB

Overview

This skill audits an iOS app repository (Swift/Xcode, React Native bare, or Expo) for App Store/TestFlight compliance and release readiness. It produces a clear PASS/WARN/FAIL verdict, a list of evidence-backed checks with remediation steps, and a practical publish checklist developers can tick off. The audit is read-only by default and flags any checks that would require macOS/Xcode or explicit mutating actions.

How this skill works

The auditor detects the project flavour (Expo, React Native, or native iOS) and extracts key identifiers (bundle id, version, build). It runs static compliance checks across repo hygiene, icons, launch screen, privacy/permission strings, ATS settings, third‑party SDK notices, and store listing basics. Optionally, when Xcode is available, it can run build-accuracy checks (scheme listing and a simulator Release build) and mark signing/archive steps as MUTATING. The final report includes per-check evidence, remediation steps, and a manual checklist for items the agent cannot verify.

When to use it

Before submitting a new app or update to App Store Connect/TestFlight
When preparing a monorepo app directory for a release candidate
To audit privacy and permission disclosures before privacy review
When you need a quick pass/warn/fail readiness signal without building
To validate icon, launch screen, and store listing prerequisites

Best practices

Run the read-only audit from the repo root or the app subdirectory to detect flavour reliably
Keep fixes in-repo small and explicit; ask before running any mutating commands
Perform build-accuracy checks on macOS with Xcode to upgrade WARNs to confident PASSes
Include privacy policy URL and contact/support info in the repo/docs to avoid listing warnings
Treat manual checklist items (metadata, screenshots, export compliance) as release blockers even if automated checks pass

Example use cases

Validate a React Native app in a monorepo before handing to QA for TestFlight
Audit an Expo managed app for missing App Store icon, launch image, or permission strings
Run a quick compliance sweep to find ATS exceptions or exposed secrets in a native iOS project
Generate a publish checklist for a teammate responsible for App Store Connect metadata
Switch to fix-mode to apply safe in-repo patches for missing Info.plist permission strings

FAQ

No. The default is read-only. Build or archive steps that modify the workspace are only run if you explicitly request them; they will be labeled MUTATING.

Can this guarantee my App Store submission will be accepted?

No. The audit finds technical and packaging issues and highlights risks, but App Store review decisions and some metadata/legal checks remain manual and outside automated verification.

What happens if Xcode is not available?

Build-accuracy checks are skipped and the overall verdict will remain WARN for areas that require a build; static checks still produce PASS/WARN/FAIL results.