{"id":77651,"plugin_id":"plugins_6ae8cc5ee77c81918ab31ed7701a28de","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-03T00:15:27.269Z","digest":"e9e53e13f4dcab50a4ef7a1277fa4490f1a3dcf5dbf214a082f1f4f9ebe1732d","against":null,"payload":{"description":"Prepare tested web/PWA/iOS/Android applications for deployment, store submission or handoff with accurate platform gates, security findings and user approvals.","included_files":[],"name":"prepare-release","skill_md_contents":"---\nname: prepare-release\ndescription: Prepare tested web/PWA/iOS/Android applications for deployment, store submission or handoff with accurate platform gates, security findings and user approvals.\n---\n\n# Prepare Release\n\n1. Read `../../references/release-and-compliance.md` and `../../references/testing-and-evidence.md`. Determine actual target (preview, staging, production, TestFlight, App Store, Play Console, distributable ZIP).\n2. Confirm app identifier, version, environments, signing, legal/privacy copy, runtime secrets, data retention, content policy and platform permissions. Do not invent organization identities, privacy policies or store screenshots.\n3. Run available build/test/security/accessibility checks and attach evidence. Provide platform-specific blockers (macOS/Xcode for Apple signing, keystore/Android build tools for Android, HTTPS for PWAs, DNS for web).\n4. Prepare deployment checklist, release notes, rollback/backup strategy and known issues. Ask for user approval before deploy, public sharing, purchases, external writes or app-store submission.\n5. Return a verified release bundle where tools support it; otherwise a clearly labeled release-readiness report, not a false publication claim.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}