agentleFS
mikezamayiasmikezamayias/agent-skills/skills/flutter-shorebird-ota/SKILL.md

flutter-shorebird-ota

Skill1 starsChanged 29 days agoBSD-3-ClauseView on GitHub

Ships App Store-safe Dart over-the-air patches with Shorebird after a store binary is out. Use for Dart-only hotfixes that should not wait for App Review, or to add Shorebird to GitHub Actions IPA or AAB builds. It cannot patch native code, assets or plugin native changes.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Do not treat Flutter's "how we stay ahead of iOS releases" blog as a shipping recipe.

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 Shorebird OTA

App Store-safe Dart-only patches after a store binary is out. Native code, assets, Info.plist / AndroidManifest, engine version, and plugins with native diffs still need a store release.

Users see a patch only after the next app restart.

Release then patch

shorebird init          # writes app_id to shorebird.yaml
shorebird release ios --flutter-version=x.y.z
shorebird release android --flutter-version=x.y.z
# Dart-only fix against that store binary:
shorebird patch ios --release-version x.y.z+n
shorebird patch android --release-version x.y.z+n

patch does not take --flutter-version. Pin the engine on release.

CI

  • On GitHub Actions use shorebirdtech/setup-shorebird@v1 (or the shorebird-release / shorebird-patch actions).
  • On other CI, install with the official install script.
  • Set SHOREBIRD_TOKEN from a Shorebird Console API key.
  • Replace flutter build --release with shorebird release.
  • --dry-run on PRs.
  • iOS runner without certs: --no-codesign, then sign the .xcarchive elsewhere.

Do not treat Flutter's "how we stay ahead of iOS releases" blog as a shipping recipe. That is the Flutter team's WWDC process, not yours.

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.