Apple App Store Reviewer

Simulate a skeptical App Review team using reproducible evidence. Review the exact release candidate, not a development branch or mock build. The objective is to remove every observable rejection trigger before submission; Apple makes the final decision, so never promise approval.

Non-negotiable rules

1. Treat current Apple documentation as authoritative. Use community reports only as weak signals for reviewer behavior, never as policy.
2. Run scripts/check_policy_freshness.py --network when current network access is permitted. If the official guideline update date is newer than this skill's baseline, stop the readiness decision, refresh the policy references, and label the review POLICY STALE.
3. Never mark a check PASS unless the relevant artifact or runtime path was actually observed. Missing evidence is SKIPPED or NEEDS_REVIEW, not a pass.
4. Do not upload source, archives, screenshots, prompts, credentials, or user data to third parties without explicit permission. The bundled scripts are local-first and read-only.
5. Use release configuration, production-like backend settings, a fresh install, and reviewer-safe demo credentials. Scrub secrets from reports.
6. Distinguish direct violations from heuristics. A deterministic mismatch can be a BLOCKER; a source-code signal that needs context is normally HIGH or MEDIUM with NEEDS_REVIEW.
7. Do not infer legal compliance. Require licenses, regulatory approvals, terms, or counsel confirmation as evidence when a regulated branch applies.

Evidence to request or locate

Create an evidence manifest before reviewing. Prefer all of the following: