Imported from PhantomBeast2090/Crave_IOS (
.opencode/skills/crave-release/SKILL.md). Install upstream withnpx skills add PhantomBeast2090/Crave_IOS --skill crave-release. Copyright stays with the author.
Crave Release
Audit before every release. Never claim release readiness without evidence — each check below needs a verified result, not an assumption.
Audit checklist
- Production configuration: Supabase URL/anon key point at production;
Secrets.swiftpresent via secure provisioning, never committed;AppConfig.isBackendConfiguredtrue; no staging/test endpoints. - Secrets: no keys in source, logs, screenshots, or crash reports; Razorpay uses production key material server-side only.
- Entitlements/capabilities match usage (camera for vendor QR scan with
NSCameraUsageDescriptionset and justified). - Privacy: permission strings accurate; privacy manifests and required-API reasons current; notification usage matches what is configured.
- Payments: production Razorpay/Edge Function configuration verified with a real (reversible) transaction path; failure and refund paths reachable.
- Supabase: production RLS/migrations applied (001–012 verified, including the
012_admin-stats fix); realtime and Edge Functions healthy. - Quality gates: clean build, full test suite green (
crave-testing), QA pass (crave-qa), security pass (crave-security), performance sanity (crave-performance). - Crash risks: force-unwraps on network/decode paths,
fatalErroronModelContainercreation (degraded-launch path?), unhandled End-of-flow states. - App Store: version/build numbers, icons, launch screen, screenshots/metadata
if requested; route review-policy depth to
app-store-review.
Rules
- Produce a go/no-go with P0 blockers listed first and evidence per item.
- Any release-blocker fix re-enters through
crave-muse-protocol(implement → validate → audit), not as a hot tweak.