What problem does it solve? Release builds for Flutter apps involve a fragile sequence of steps — cleaning, fetching dependencies, baking in environment variables, enabling obfuscation, and versioning correctly — where a single missed step causes Play Console rejections or unsymbolized crash reports. ## Core Features & Use Cases - Full release pipeline: Runs flutter clean, flutter pub get, and flutter build appbundle --release with --dart-define-from-file=env/prod.json, --obfuscate, and --split-debug-info via tools/build_release.sh. - Pre-build sanity checks: Verifies env/prod.json exists and prompts to bump the versionCode (+N suffix) in pubspec.yaml so Play Console does not reject a duplicate upload. - Post-build reporting: Reports the AAB path, file size, and reminds you to preserve build/symbols/ for Crashlytics symbolication without committing it. - Use Case: Before submitting a new Woody marketplace release to Google Play, run this skill to produce an obfuscated, environment-configured AAB with symbols archived for later crash analysis. ## Quick Start Ask the assistant to run the build-release command to produce a production AAB, confirming the version code bump when prompted.
