Flutter release
Building and publishing a Flutter app to the App Store and Google Play — build appbundle/ipa, signing, obfuscation, submission checklists. Apply when preparing a release, a beta test, or a store rollout.From its SKILL.md
npx -y skills add Neznakometz/StackForge --skill flutter-releaseAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.6 KB, 369 tokens by cl100k_base, as published. Nobody here has run it
Flutter — release to the stores
Source: docs.flutter.dev/deployment.
Android (Google Play)
- Build:
flutter build appbundle→build/app/outputs/bundle/release/app-release.aab(AAB — the preferred Play format). R8 shrinker is on by default. - Signing: upload-keystore →
android/key.properties+signingConfigsinandroid/app/build.gradle. Do NOT commit the keystore and passwords.applicationId,versionCode/versionNamefrompubspec version:. - Checklist: review the manifest/permissions, release signing, build the AAB, upload to Play Console (Play App Signing).
iOS (App Store)
- Build:
flutter build ipa→.xcarchiveinbuild/ios/archive/,.ipainbuild/ios/ipa/. - Signing: in Xcode (Team, bundle id, provisioning); register the bundle id in App Store Connect ahead of time.
- Submit:
.ipavia Apple Transport /xcrun altool/ Xcode Organizer → fill in the listing in App Store Connect.
Required for both
- Obfuscation:
--obfuscate --split-debug-info=<dir>; keep symbols for de-obfuscating stack traces. - Beta: TestFlight (iOS) / closed track (Android) → gradual rollout (10→50→100%).
- Size: watch the build weight (one of the migration goals); keep the art budget under control.
CI/CD
fastlane / Codemagic / GitHub Actions — docs.flutter.dev/deployment/cd. AAB path for fastlane: ../build/app/outputs/bundle/release/app-release.aab.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most ship operate skills give in 369 tokens
Counted across 779 of the 1,178 authors here whose files we hold, read 2026-08-07
- Document a rollback plan before deploymentin 41 of 779, across 22 files
- Update the changelogin 21 of 779, across 19 files
- Run the test suitein 20 of 779
- Create an annotated git tagin 20 of 779
- Clean up feature flags after full rolloutin 18 of 779, across 10 files
- Verify deployment health after launchin 18 of 779, across 10 files
- Test both feature flag statesin 17 of 779, across 9 files
- Verify the working tree is cleanin 17 of 779
- Make database migrations backward-compatiblein 16 of 779, across 8 files
- Set up error monitoring before launchin 15 of 779, across 7 files
- Monitor metrics at each rollout stagein 14 of 779, across 5 files
- Create a GitHub releasein 14 of 779
Said here and by no other author read
- build the appbundle for Google Play
- configure android signing in key.properties
- review the manifest and permissions
- build the ipa for the App Store
- configure ios signing in Xcode
- register the iOS bundle id in App Store Connect
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.