shorebird-patch
Shorebird Patch automates the creation and staging of over-the-air patches for iOS and Android apps. The skill handles patch generation, asset difference validation, and staging distribution, while leaving production promotion to manual user control after verification. Use this when you need to push updates without a full release.
Shorebird Patch creates and stages OTA patches for mobile apps, with manual promotion to production.
AI-generated summary based on this skill's SKILL.md
Install
K9i-0/ccpocket/shorebird-patch · repository language: Dart
git clone https://github.com/K9i-0/ccpocket
cp -r ccpocket/.claude/skills/shorebird-patch ~/.claude/skills/shorebird-patchFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I create a shorebird OTA patch for staging?
Shorebird Patch automates patch creation by generating over-the-air updates for your iOS and Android apps. To create a staging patch, initiate the patch generation workflow, which automatically handles asset differences and prepares the patch for staging distribution. Shorebird Patch validates all asset changes during this process and flags any warnings before the patch moves forward.
What does shorebird patch distribution to staging involve?
Shorebird Patch manages the full staging distribution workflow for OTA patches. Once your patch is created and validated, Shorebird Patch handles the distribution to your staging environment, ensuring asset changes are properly tracked and any patch warnings are surfaced for your review before you proceed to production promotion.
How do I promote a shorebird patch from staging to stable?
Shorebird Patch leaves production promotion under your manual control after verification. Once your staging patch has been validated and you've confirmed there are no asset warnings or issues, you can promote the verified patch to stable production through Shorebird Patch's promotion workflow.
How does shorebird patch handle versioning across iOS and Android?
Shorebird Patch manages patch versioning and tracks patch numbers across both iOS and Android platforms. The skill maintains consistent version tracking so you can monitor which patches have been deployed to each platform and ensure your mobile app updates stay synchronized.
What validation does shorebird patch perform on asset changes?
Shorebird Patch validates all asset changes and handles patch warnings as part of its verification process. Before staging distribution, the skill checks for asset differences and surfaces any warnings, giving you visibility into what's changing so you can address concerns before promoting to production.
SKILL.md
rendered from the published skill — quoted content, verbatim
Shorebird パッチ配布
Shorebird OTA パッチを staging に作成する。stable への昇格はユーザーが検証後に手動で実施する。
> 新バージョンのリリースは /release-mobile スキルを使用する。
> アセット差分でパッチが適用されない場合も、/release-mobile でリリース後に再パッチする。
フロー概要
patch (staging) → デバッグ画面で検証 → ユーザーが promote (stable) → 全ユーザーに配信
パッチ手順
1. バージョン確認
grep '^version:' apps/mobile/pubspec.yaml
version: X.Y.Z+N の値を記録する（= <version>）。
2. パッチ作成 (staging)
引数でプラットフォームが指定された場合はそのまま使う。指定がなければ、その時点のエージェントで利用可能な質問手段でユーザーに確認する。特定の質問ツール名には依存しない。
# iOS
bash .claude/skills/shorebird-patch/patch.sh ios <version>
# Android
bash .claude/skills/shorebird-patch/patch.sh android <version>
# 両方の場合は順番に実行
スクリプトが以下を一括で行う:
- shorebird patch で staging にパッチ作成
- --allow-asset-diffs によりアセット変更の確認プロンプトを自動スキップ
完了後の出力から パッチ番号 を記録する（= <patch-number>）。
3. アセット差分の検証（重要）
パッチ出力に以下の警告が含まれていないか確認する:
``` [WARN] Your app contains asset changes, which will not be included in the
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 3 files
.claude/skills/shorebird-patch/SKILL.md
.claude/skills/shorebird-patch/patch.sh
.claude/skills/shorebird-patch/promote.sh