agentleFS
thiennc-tesoglobalthiennc-tesoglobal/flutter-skills/skills/flutter-build-release/SKILL.md

flutter-build-release

Skill16 starsChanged 3 months agoBSD-3-ClauseView on GitHub

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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read SDK constraints, flavors/schemes, bundle/application IDs, version source, signing configuration, environment injection, CI, native …

    line 12
  2. Distinctive:

    Keep environment selection explicit and fail safely when required values are missing.

    line 16
  3. Distinctive:

    Treat obfuscation as code-hardening, not secret protection.

    line 20
  4. Distinctive:

    Read flavor and scheme alignment when coordinating product flavors, Xcode schemes, application IDs, and service configuration files.

    line 31
  5. Distinctive:

    Read obfuscation and symbols when configuring Dart AOT obfuscation, symbol splitting, mapping archives, or stack trace deobfuscation.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.