release-ios-appstore
Skill40 starsChanged 4 days agoApache-2.0View on GitHub
Use when releasing, submitting, or verifying a public Hussh One iOS App Store build cut from green main: Apple-managed signing with an Admin ASC API key, a binary whose backend is chosen by `backend_target` (production by default; explicit legacy UAT diagnostics), per-version "What's New" and build attach via the ASC API, and the two-gate dispatch path (prepare-only default, opt-in irreversible public submit).
In this repository69 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hushh-webapp/AGENTS.mdAGENTS.md
- impeccableSkill
- agent-orchestration-governanceSkill
- analytics-observability-governanceSkill
- animateSkill
- animation-vocabularySkill
- apple-designSkill
- autonomous-rca-governanceSkill
- backend-agents-operonsSkill
- backend-api-contractsSkill
- backend-runtime-governanceSkill
- backendSkill
- brandkitSkill
- client-env-paritySkill
- codex-skill-authoringSkill
- comms-communitySkill
- context-refreshSkill
- contributor-onboardingSkill
- docs-governanceSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- founder-brief-curationSkill
- frontend-architectureSkill
- frontend-cache-coherenceSkill
- frontend-design-systemSkill
- frontend-native-surface-mapperSkill
- frontendSkill
- frontend-surface-placementSkill
- future-plannerSkill
- github-contribution-governanceSkill
- hushh-consent-mcpSkill
- hushh-icon-themeSkill
- iam-consent-governanceSkill
- imagegen-frontend-mobileSkill
- imagegen-frontend-webSkill
- improve-animationsSkill
- industrial-brutalist-uiSkill
- kai-test-account-resetSkill
- less-text-karma-jiSkill
- mcp-developer-surfaceSkill
- mobile-nativeSkill
- mobile-parity-auditSkill
- mobile-plugin-contractsSkill
- morphy-axSkill
- one-voice-governanceSkill
- oss-license-governanceSkill
- pdf-artifact-generationSkill
- pick-ui-librarySkill
- pkm-upgrade-rehearsalSkill
- planning-boardSkill
- pr-governance-reviewSkill
- profile-uiSkill
- prototypeSkill
- puppy-one-harnessSkill
- quality-contractsSkill
- repo-contextSkill
- repo-operationsSkill
- review-animationsSkill
- reviewer-app-testingSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Avoid overlap with uat-scoped-deploy, mobile-native, and broad repo-operations intake.
- Very specific: line 64
Verify from the ASC API and the run Job summary — uploaded, processed, "What's New" set, build attached, submitted-or-prepared — before …
- Very specific: line 70
If the request is broad or ambiguous, route it back to repo-operations.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Hussh Release iOS to App Store Skill
Purpose and Trigger
- Primary scope:
release-ios-appstore-scope - Trigger on releasing, submitting, or verifying a public iOS App Store build from a green
mainSHA. - Avoid overlap with
uat-scoped-deploy,mobile-native, and broadrepo-operationsintake.
Coverage and Ownership
- Role:
spoke - Owner family:
repo-operations
Owned repo surfaces:
.github/workflows/release-ios-appstore.ymlscripts/release/dispatch-ios-appstore.mjs
Non-owned surfaces:
mobile-nativeuat-scoped-deploysecurity-auditrepo-operations
Do Use
- Cutting a public App Store build from the latest green
main(prepare-only by default). - Setting per-version "What's New", attaching the processed build, and resolving the build number.
- Verifying an App Store Connect upload/version/submission state after a "Release iOS to App Store" run.
Do Not Use
- TestFlight-only distribution — use the
ship-ios-testflightsibling (same UAT-backed binary). - Merging code to
main; this ships what is already onmainand never merges. - Production Cloud Run deploys route to
repo-operations; scoped UAT deploys route touat-scoped-deploy. - Publish-safety clearance or consent-boundary decisions — route to
security-audit.
Read First
.github/workflows/release-ios-appstore.ymldocs/operations/mobile/release-ios-appstore.mdscripts/release/dispatch-ios-appstore.mjsscripts/ci/submit-appstore-version.pyscripts/ci/resolve-ios-build-number.pydeploy/app_store_deployment.md.agents/skills/repo-operations/references/admin-release-sop.md.agents/skills/release-ios-appstore/references/release-proof.md
Workflow
- Confirm the
ghactor and rerunner have currentdeploy-productionteam membership through the trusted admission check. Saved username lists and organization-admin status do not grant release authority. - Pick SHA = user-provided else latest
origin/main; it must be an ancestor oforigin/main. - Require "Main Post-Merge Smoke Gate" = success on that exact SHA (the workflow re-checks via
scripts/ci/require-deploy-sha-on-main.shand refuses otherwise). - First run after any signing/secret change, dispatch a dry run (
make ios-prod-release-dry): archive + sign, no upload. A dry run does NOT catch a closed marketing-version train. - GATE 1 (every dispatch): restate workflow,
--ref main, exact SHA, mode, production backend and bundlecom.hushh.app. Existing explicit authorization for that operation is sufficient; do not ask again. Usemake ios-prod-release ARGS="--sha <sha> --backend production --yes --whats-new '<notes>'"(prepare-only default; no--submit). Explicit UAT remains a legacy diagnostic option, not a public-release target. A backend transition for existing installations requires a reviewed recovery plan: the same Firebase UID does not transfer vaults or records between databases. - Before packaging, follow
release-proof.md→ Live version and concurrent-release admission. Read current Apple marketing versions/states and other developers' in-flight uploads; a higher build number does not advance the marketing version. Use a supported explicit--marketing-versionor reviewed source change when needed, verify app/extension/receipt parity, and preserve exact backend provenance. Resolve an approved-but-unreleased public version before preparing its successor; publishing or withdrawing it requires its own authorization. - GATE 2 (manual public submission): irreversible and publishes to real users; requires fresh explicit authorization and every publish-safety blocker cleared, then
--submit --ack-blockers(workflow inputsubmit_for_review=true). Unattended UAT/native cadence is retired; preparation never authorizes submission or publication. - Verify from the ASC API and the run Job summary — uploaded, processed, "What's New" set, build attached, submitted-or-prepared — before reporting done. Never print, paste, or read the ASC
.p8/ Key / Issuer secrets. - A production-backed submit needs the dedicated production reviewer account and its App Review Information, set by hand in App Store Connect (
docs/operations/mobile/release-ios-appstore.md§ App Review sign-in on a production-backed build). Production never advertises or mints review mode (consent-protocol/api/routes/health.py), so do not "enable"APP_REVIEW_MODEthere, and never reuse the production reviewer UID as a UAT or devREVIEWER_UID: the lanes share one Firebase authority and UAT mints with no credential. - Any verify step shared with the TestFlight sibling must bring the same runtime. Run 36358944003 (2026-09-27) died in
verify:one-voiceonModuleNotFoundError: dotenv: the capability-graph generator needs the consent-protocol package, TestFlight got its Python step in 231c6e50f, and this lane did not. Diff both workflows' setup steps whenever a verify step is shared.
Handoff Rules
- If the request is broad or ambiguous, route it back to
repo-operations. - Route iOS native/Capacitor build, entitlement, or plist issues to
mobile-native. - Route production Cloud Run and web deploys to
repo-operations; route scoped UAT deploys touat-scoped-deploy. - Route publish-safety, consent, or secret-boundary findings to
security-audit.
Required Checks
gh run list --workflow release-ios-appstore.yml --limit 5 --json databaseId,status,conclusion,headSha,event,url
gh workflow view release-ios-appstore.yml
python3 .agents/skills/codex-skill-authoring/scripts/skill_lint.pyDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

