CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

flutter-build-release

Configure and verify Flutter flavors, environments, signing, versioning, release artifacts, obfuscation symbols, and store-ready builds. Use for local artifact configuration; route CI provider workflows to flutter-ci-cd, and do not publish or change live credentials without explicit authorization.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is thiennc-tesoglobal/flutter-skills

SKILL.md
Quality
Evals
Security

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

  • Flutter deployment
  • Build and release an Android app
  • Build and release an iOS app
  • apksigner
Repository

thienqo/flutter-skills

Path

skills/flutter-build-release/SKILL.md

Last updated
First committed

Canonical home

thiennc-tesoglobal/flutter-skills
In sync

since Aug 24, 2026

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.