mobile-release
/mobile-release
Przygotowuje wydania aplikacji mobilnych: wersje, podpisy, symbole, gotowość do sklepu, rollout i pipeline CI/CD.
- Autor
- wrsilva ↗
- Repozytorium
- reis-mobile ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 11
- Skrypty
- 1
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
- 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: scripts/verdict.mjs
Co robi i kiedy
Przygotowuje wydania aplikacji mobilnych: wersje, podpisy, symbole, gotowość do sklepu, rollout i pipeline CI/CD.
Oryginalny opis (EN)
Prepares mobile releases across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform, including separate Android/iOS artifacts from a shared KMP revision. Covers versions, signing, symbols, store readiness, rollout, release notes and CI/CD. Use for release audits, store submission, build pipelines or rollout planning.
Jak działa
- 1. Pick the references
- 2. Readiness checklist
- 3. Report
Podgląd SKILL.md
--- name: mobile-release description: Prepares mobile releases across Flutter, native Android, native iOS, React Native and Kotlin Multiplatform, including separate Android/iOS artifacts from a shared KMP revision. Covers versions, signing, symbols, store readiness, rollout, release notes and CI/CD. Use for release audits, store submission, build pipelines or rollout planning. intents: [release, deployment] stacks: ["*"] --- # Mobile Release One release process for every mobile stack. This file holds the process and what is true everywhere; each platform's versioning, signing, symbols and store details live in its reference. ## 1. Pick the references | Need | Read | |---|---| | Evidence-backed readiness audit, verdict and report | [references/readiness.md](references/readiness.md) | | Flutter app | [references/flutter.md](references/flutter.md) | | Native Android, or the Android build of any app | [references/android.md](references/android.md) | | Native iOS, or the iOS build of any app | [references/ios.md](references/ios.md) | | React Native or Expo app | [references/react-native.md](references/react-native.md) | | Kotlin Multiplatform shared module and both host apps | [references/kotlin-multiplatform.md](references/kotlin-multiplatform.md) | | In-app purchases and subscription lifecycle | [references/billing.md](references/billing.md) | | Release notes and store listing text | [references/store-copy.md](references/store-copy.md) | | A CI/CD pipeline that builds, signs and uploads | [references/ci-cd.md](references/ci-cd.md) | Flutter and React Native apps also need the Android and iOS references for signing and store details. Deeper platform guides live in the platform skills: Google Play policy and Play Billing in `mobile-android`, TestFlight and App Store Connect in `mobile-ios`, EAS in `mobile-rn`. Security hardening before release is in `mobile-security`, and production crash, error and release-health signals are in [mobile-observability](../mobile-observability/SKILL.md). ## 2. Readiness checklist For readiness audits, first follow [the readiness contract](references/readiness.md): resolve each artifact identity, collect per-target evidence and apply its required gates and deterministic verdict helper. Check each item against the project, not against memory. For the readiness verdict, a missing artifact or unavailable check is **unknown**; use **fail** only for an observed failure with evidence. Record a source reference and next action for every gate. **Version** - [ ] The version name follows the app's actual versioning scheme and is verified in the artifact and applicable CI overrides. - [ ] The build number satisfies the destination store’s numbering scope, verified against upload history: Android versionCode increases across tracks; iOS build numbers must be unused within the applicable version train. See the native references. - [ ] Android, iOS and any cross-platform manifest (`pubspec.yaml`, `app.json`) agree on the version. **Build quality** - [ ] CI is green on the release commit: lint or analysis, tests, and a release build for each platform. - [ ] The release build is the one tested: release configuration, production environment, real signing — not a debug build. - [ ] No debug leftovers: logging of sensitive data, debug menus, test endpoints, `debuggable` or development entitlements, feature flags pointing at staging. - [ ] Crash symbols for this exact build are uploaded or archived: R8 mapping, dSYMs, Dart debug info, JavaScript source maps. **Store and compliance** - [ ] The target SDK, minimum OS and build toolchain meet the store's current requirements. These change every year: tell the user to confirm them in the Play Console and Apple's upload requirements instead of stating dates from memory. - [ ] New permissions, tracking or data collection are reflected in the Play Data safety form, the App Store privacy details, privacy manifests and the privacy policy. - [ ] Reviewers can reach every feature: a demo account and notes for anything behind login, hardware or location. - [ ] Release notes and, when features changed, screenshots and description are ready in every listed language. **Rollout** - [ ] Staged rollout (Play) or phased release (App Store) planned for updates, with the crash-free and ANR metrics to watch and the threshold that halts it. - [ ] Rollback plan: stores do not roll back a binary. Halting a rollout stops new installs; users who updated need a new build with a higher build number, a server-side kill switch or a remote config flag. Know which one applies before shipping. - [ ] The release commit is tagged and the tag matches the version, when this is the project's release convention. ## 3. Report Use the [readiness report and decision rules](references/readiness.md#report). Any failed or unknown required gate means **NO-GO**. **GO WITH RISKS** requires all gates to pass with explicitly documented non-blocking risks; **GO** requires no outstanding risks. Readiness audits inspect existing evidence without running builds/tests or modifying the app. Version bumps, tags, uploads and store changes follow the user's explicit execution scope and existing authorization.
Pliki w paczce (11)
- SKILL.md 5 KB
- references/android.md 4 KB
- references/billing.md 8 KB
- references/ci-cd.md 6 KB
- references/flutter.md 3 KB
- references/ios.md 4 KB
- references/kotlin-multiplatform.md 1 KB
- references/react-native.md 3 KB
- references/readiness.md 9 KB
- references/store-copy.md 3 KB
- scripts/verdict.mjs 3 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · wrsilva/reis-mobile | 90 | MIT |
| avelikiy/great_cto | 100 | MIT |
| nimadorostkar/Claude-Skills-collection | 100 | MIT |
| bex-co/beancount-io | 95 | MIT |
| wrongstack/wrongstack | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki bb2bea6e782b (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100mobile-ci
Konfiguruje i przegląda CI/CD mobilne oraz automatyzację fastlane dla Fluttera, Androida, iOS, React Native i KMP. - 90mobile-accessibility
Audytuje i naprawia dostępność aplikacji mobilnych we Flutter, Androidzie, iOS, React Native i KMP, z etykietami dla czytników ekranu. - 90flutter-core:flutter-deployment
Przygotowuje wydanie aplikacji Flutter na Androida, iOS, web i desktop: konfigurację budowania, podpisy, sklepy i CI/CD. - 85mobile-engineering
Projektuje, wdraża i przegląda aplikacje mobilne Flutter, React Native, iOS i Android, z trybem offline, wydajnością i publikacją w sklepach. - 100wai-mobile-release
Konfiguruje jednorazowo budowanie, podpisywanie i wysyłkę aplikacji iOS lub Android do sklepów: Fastlane, TestFlight, Play Console. - 100mobile-dev
Wspiera tworzenie aplikacji mobilnych na iOS, Androida i React Native: budowa aplikacji i ekranów, debugowanie buildów iOS oraz optymalizacja wydajności Androida.