release-check
/release-check
Sprawdza projekt Flutter przed budową dla Google Play lub App Store, żeby wykryć braki zanim wydanie zostanie odrzucone.
- Autor
- ChandraChaan ↗
- Repozytorium
- flutter-release-kit ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 08.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 4
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 08.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Sprawdza projekt Flutter przed budową dla Google Play lub App Store, żeby wykryć braki zanim wydanie zostanie odrzucone.
Wyzwalacze z opisu
Argumenty
/release-check [--skip-tests] [--platform android|ios|all]
Oryginalny opis (EN)
Run a release preflight on a Flutter project before building for Google Play or the App Store. Use when the user asks "is my app ready to release", "check before I publish", "release checklist", "why was my app rejected", or before running flutter build appbundle / ipa.
Jak działa
- Step 1: run the deterministic preflight
- Step 2: investigate every FAIL and WARN
- Step 3: check things the script cannot
- Step 4: report
Podgląd SKILL.md
---
name: release-check
description: Run a release preflight on a Flutter project before building for Google Play or the App Store. Use when the user asks "is my app ready to release", "check before I publish", "release checklist", "why was my app rejected", or before running flutter build appbundle / ipa.
argument-hint: "[--skip-tests] [--platform android|ios|all]"
allowed-tools: Bash(bash ${CLAUDE_PLUGIN_ROOT}/scripts/preflight.sh *), Read, Grep, Glob
---
# Release check
You are helping a Flutter developer ship a release that will not be rejected by Google Play or App Store review. Be concrete: name the file and the exact change for every problem.
## Step 1: run the deterministic preflight
From the Flutter project root run:
```bash
bash "${CLAUDE_PLUGIN_ROOT}/scripts/preflight.sh" $ARGUMENTS
```
The script prints `OK` / `WARN` / `FAIL` lines grouped by section (Version, Changelog, Static analysis, Tests, Debug leftovers, Android, iOS) and exits 1 on any FAIL. It may take a minute when tests run. If the user is clearly in the middle of development and only wants a quick look, pass `--skip-tests`.
## Step 2: investigate every FAIL and WARN
For each item, open the file the script names and confirm the finding before reporting it. Common fixes:
| Finding | Fix |
|---|---|
| Version has no build number | Change `version: 1.2.0` to `version: 1.2.0+1` in `pubspec.yaml`. |
| Tag already exists for this version | Run the `bump-version` skill. |
| `com.example` applicationId or bundle id | Use `flutter pub run change_app_package_name:main com.yourco.app` or edit `android/app/build.gradle(.kts)` and the three `PRODUCT_BUNDLE_IDENTIFIER` entries in `ios/Runner.xcodeproj/project.pbxproj`. |
| Release signs with debug key | Add `key.properties` loading and a `release` signingConfig; see `references/android-signing.md`. |
| `key.properties` or `*.jks` tracked by git | Add to `.gitignore`, then `git rm --cached <file>`; rotate the keystore password if the repo is public. |
| No `PrivacyInfo.xcprivacy` | Create `ios/Runner/PrivacyInfo.xcprivacy`; template in `references/privacy-manifest.md`. |
| `debuggable=true`, cleartext traffic, localhost URLs | Remove before release. |
| Analyzer errors / failing tests | Fix them; do not suggest skipping. |
## Step 3: check things the script cannot
Look at the project and consider:
- **Target SDK**: Google Play requires new apps and updates to target a recent Android API level (Play's rolling requirement is roughly the previous year's release). Check `targetSdk` in `android/app/build.gradle(.kts)` or the Flutter default.
- **App icon and splash**: the default Flutter icon is a rejection in review and an instant uninstall for users. Check `flutter_launcher_icons` / `flutter_native_splash` config or the mipmap folders.
- **Permissions**: if the manifest has anything beyond INTERNET, suggest running the `permission-audit` skill.
- **Store assets**: feature graphic 1024x500 (Play), screenshots for each required device class, privacy policy URL (required if the app collects any data or requests sensitive permissions).
- **Account deletion**: both stores require an in-app account deletion path if the app supports account creation.
- **Login for reviewers**: if there is a login screen, remind the user to supply a demo account in the review notes.
Read `references/store-rejections.md` for the full list of common rejection reasons and their fixes when the user asks why they were rejected or wants a deeper review.
## Step 4: report
Return a short report:
1. **Verdict**: READY / NOT READY.
2. **Must fix** (FAIL items, each with file and exact change).
3. **Should fix** (WARN items that matter for this app).
4. **Next commands**: usually `flutter build appbundle --release` and `flutter build ipa --release`, preceded by `bump-version` and `changelog` when the version was already shipped.
Keep it tight. Do not repeat OK lines unless the user asks for the full output.
Pliki w paczce (4)
- SKILL.md 4 KB
- references/android-signing.md 3 KB
- references/privacy-manifest.md 3 KB
- references/store-rejections.md 5 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · ChandraChaan/flutter-release-kit | 100 | MIT |
| Thank-you-Linus/Linus-Dashboard | 100 | MIT |
| mohibshaikh/clawvet | 100 | MIT |
| hugrverk/riggverk | 90 | MIT |
| Er2oneousbit/claude-code-game-kit | 86 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 9608f207b929 (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
- 100release
Przygotowuje wydanie aplikacji Flutter: podbija wersję, changelog, flavory, obfuskowane buildy AAB i IPA oraz listę kontrolną sklepu. - 100flutter-release-readiness
Sprawdza aplikację Flutter przed wysyłką do Google Play lub App Store: podpisy, wersje, manifest prywatności i listy kontrolne. - 100prompt-to-store
Prowadzi aplikację Flutter od jednozdaniowego zlecenia do wersji testowej na telefon, a potem do Google Play i App Store. - 100flutter-store-cd
Konfiguruje i naprawia ciągłe dostarczanie Flutter do App Store i Google Play przez GitHub Actions, z podpisami i kluczami. - 90store-listing
Pisze lub sprawdza opisy aplikacji Flutter do Google Play i App Store: tytuł, podtytuł, opisy, słowa kluczowe i uwagi do wydania. - 100flutter-release
Buduje, podpisuje i wysyła aplikację Flutter do testerów i sklepów przez Fastlane oraz CI, także z podpisami iOS.