mcpField
F
flutter-build-release

flutter-build-release

github.com/thienqoCloud & DevOps1374 installsUpdated 1d ago
Repository

About flutter-build-release

A build and release skill for Flutter projects that guides reproducible platform artifacts while protecting signing material and release authority. It supports workflows that verify builds, signatures, and release readiness.

Key features

  1. 01Inspect version, environment, and signing configuration
  2. 02Build artifacts for requested platforms and environments
  3. 03Verify artifact signatures and signing identity
  4. 04Run formatting, analysis, and tests
  5. 05Keep symbols needed for crash deobfuscation
  6. 06Require authorization before publishing actions

Use cases

  1. 01Produce a release artifact for a target and flavor
  2. 02Verify signatures for APK, AAB, or iOS bundles
  3. 03Check metadata and critical flows before release
  4. 04Record artifact paths, versions, and remaining release work

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/thienqo/flutter-skills --skill flutter-build-release

After installing, type/flutter-build-releasein Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

evals/
cases.json
references/
flavor-and-scheme-alignment.md
obfuscation-and-symbols.md

Details

From the project README

Flutter Build and Release

Produce reproducible artifacts for the requested platforms while preserving secrets and external-release authority.

Preflight

Read SDK constraints, flavors/schemes, bundle/application IDs, version source, signing configuration, environment injection, CI, native deployment targets, and store requirements. Never print or commit secrets, keystores, provisioning material, or service credentials.

Rules

  • Keep environment selection explicit and fail safely when required values are missing.
  • Align Dart defines, Android variants, Apple schemes/configurations, and service files by environment.
  • Increment versions according to the repository's release policy.
  • Build the exact requested artifact and keep symbols needed for crash deobfuscation.
  • Treat obfuscation as code-hardening, not secret protection.
  • Validate icons, names, permissions, privacy declarations, and target-specific metadata.
  • Make CI use pinned or declared tool versions where practical.
  • Require explicit authorization immediately before store upload, signing-credential mutation, tagging, or publishing.

Verification

Run formatting, analysis, tests, and a clean release build for each intended target/flavor. Verify the produced artifact's signature without uploading it: apksigner verify --print-certs for an APK, jarsigner -verify -certs for an AAB, and codesign --verify --deep --strict for an iOS app bundle, then compare the certificate or signing identity with the intended release key. Install or serve the built artifact and smoke-test startup plus a critical flow. Record artifact path, version, flavor, target, and remaining store-side work.

References

  • Read flavor and scheme alignment when coordinating product flavors, Xcode schemes, application IDs, and service configuration files.
  • Read obfuscation and symbols when configuring Dart AOT obfuscation, symbol splitting, mapping archives, or stack trace deobfuscation.

Sources

Comments

Markdown supported