yakoub-ai/flutterforge · Archived

flutter-release-readiness

>- Prepare a Flutter app for Android and iOS release. Use when the user wants to run a pre-release checklist, prepare a build for the App Store or Google Play, configure signing, or check release build readiness. Trigger phrases: "prepare Flutter release", "app store Flutter", "Google Play Flutter", "release checklist", "publish Flutter app", "flutter build appbundle", "iOS archive Flutter", "sign Flutter app", "release build Flutter", "production build Flutter", "Play Store Flutter", "TestFlig…

First seen May 18, 2026

Installation

$ npx skills add yakoub-ai/flutterforge --skill flutter-release-readiness

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from yakoub-ai/flutterforge · top by installs.

npx skills add yakoub-ai/flutterforge

Browse all from yakoub-ai/flutterforge

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

License LICENSE
Default branch main
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 5,249 B
  • docs SUMMARY.md 541 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Flutter Release Readiness

Prepare a Flutter app for Android and iOS release: versioning, quality gate, signing guidance, store metadata, build commands, and CI/CD checklist.


Workflow

  1. Run universal pre-release gate (both platforms must pass before continuing).
  2. Run Android-specific checks.
  3. Run iOS-specific checks.
  4. Run quality validation — all three commands must pass.
  5. Generate docs/release/releasechecklist.md using templates/releasechecklist.md.
  6. Generate CI/CD templates if not present (from templates/github_workflows/).
  7. Present final blockers list — do not execute release builds until user approves.

NEVER run flutter build release or publish commands without explicit user approval. NEVER commit signing credentials to source control.


Universal Pre-Release Gate

  • pubspec.yaml version follows MAJOR.MINOR.PATCH+BUILD — build number strictly greater than last submission
  • CHANGELOG.md updated with this release's changes (Keep a Changelog format)
  • dart format --set-exit-if-changed . passes
  • flutter analyze --no-fatal-infos passes (zero errors; warnings documented)
  • flutter test passes — all tests green
  • No hardcoded secrets detected (run bash scripts/collectflutterlogs.sh or grep lib/ for AIza, sk-, password =, private_key)
  • .env, google-services.json, GoogleService-Info.plist are in .gitignore
  • Crash reporting / release health dashboard identified (Crashlytics, Sentry, or equivalent)
  • Rollout plan documented: staged rollout percentage, rollback threshold, first-24-hour owner

Android Checklist

  • applicationId set correctly in android/app/build.gradle
  • targetSdkVersion / targetSdk meets current Google Play policy. As of 2026-05-14, new apps and updates must target Android 15 / API level 35 or higher unless an exception applies
  • Launcher icons configured (flutterlaunchericons package or manual)
  • Adaptive icons configured for API 26+ (ic_launcher.xml)
  • Permissions in AndroidManifest.xml — remove any unused permissions
  • minSdkVersion set appropriately (Flutter minimum is 21)
  • Proguard/R8 rules present if using code shrinking
  • Signing: keystore documented (never committed); key.properties in .gitignore
  • Release build: flutter build appbundle --release
  • Play Store metadata: title (≤30 chars), short description (≤80 chars), full description (≤4000 chars), screenshots, feature graphic
  • Privacy policy URL ready
  • Play Data Safety answers prepared and match actual app behavior

iOS Checklist

  • PRODUCTBUNDLEIDENTIFIER set in ios/Runner.xcodeproj
  • App icons configured in ios/Runner/Assets.xcassets/AppIcon.appiconset
  • Launch screen configured in LaunchScreen.storyboard
  • Info.plist permission strings present for every permission requested (camera, location, microphone, etc.)
  • PrivacyInfo.xcprivacy present when required-reason APIs or third-party SDK requirements apply
  • App Store privacy details prepared; ATT reviewed if the app tracks users across apps or websites
  • MARKETINGVERSION and CURRENTPROJECT_VERSION match pubspec.yaml
  • CocoaPods up to date: cd ios && pod install --repo-update
  • Signing: Xcode managed signing or manual profile documented (never committed)
  • Release build: flutter build ios --release --no-codesign (verify then sign via Xcode)
  • App Store metadata: app name, description, keywords (≤100 chars), screenshots for required device sizes
  • Privacy nutrition labels prepared for App Store Connect

Build Commands

# Android
flutter build appbundle --release                    # Play Store (preferred)
flutter build apk --release --split-per-abi          # APK (direct installs)

# iOS
flutter build ios --release --no-codesign            # then archive via Xcode

# Run final checks first
dart format --set-exit-if-changed .
flutter analyze --no-fatal-infos
flutter test

Output Artifacts

  • docs/release/release_checklist.md — completed checklist for this release
  • .github/workflows/flutter_ci.yml — CI quality gate (if not present)
  • .github/workflows/android_build.yml — Android build workflow (if not present)
  • .github/workflows/ios_build.yml — iOS build workflow (if not present)

Cross-references

  • Agent: release-engineer
  • Templates: templates/releasechecklist.md, templates/githubworkflows/
  • Security: flutter-security skill for secrets scan before release