feat: initial react-native-update skill package

Author: sunnylqm

README.md

@@ -0,0 +1,16 @@
+# react-native-update-skill
+
+OpenClaw skill for integrating **react-native-update (Pushy)** into React Native / Expo projects.
+
+## Contents
+- `skill/react-native-update/` - skill source (SKILL.md, references, scripts)
+- `react-native-update.skill` - packaged distributable skill
+
+## Install
+Import `react-native-update.skill` into your OpenClaw skills environment.
+
+## Scope
+- Step-by-step integration guidance
+- AppKey/update.json wiring
+- iOS/Android/Expo integration checkpoints
+- Common conflict checks (e.g. expo-updates)

react-native-update.skill

@@ -0,0 +1,34 @@
+---
+name: react-native-update
+description: React Native Update / Pushy hot-update integration assistant（react-native-update 集成助手）for React Native CLI and Expo projects. Use for 安装配置, appKey/update.json 接线, iOS/Android 原生改动, 更新策略（checkStrategy/updateStrategy）, expo-updates 冲突排查, and 热更新接入 troubleshooting.
+---
+
+# React Native Update Integration
+
+## Overview
+Use this skill to get a project from “not integrated” to “hot update works in release builds”.
+Prioritize copy-paste-safe steps, smallest viable changes, and explicit verification checkpoints.
+
+## Workflow
+1. Detect app type (React Native CLI vs Expo) and target platforms.
+2. Apply dependency/install steps from `references/integration-playbook.md`.
+3. Apply required native config (Bundle URL / MainApplication integration points).
+4. Add `Pushy` client + `UpdateProvider` minimal bootstrapping.
+5. Run `scripts/integration_doctor.sh <app-root>` to detect common misses.
+6. Return a short action list: done / missing / next verification.
+
+## Guardrails
+- Keep user code changes minimal and localized.
+- Do not promise hot update works in debug mode; emphasize release verification.
+- Warn about `expo-updates` conflict in Expo projects.
+- Preserve existing app architecture; adapt snippets to current project style.
+- If native files differ heavily (monorepo/mixed native), provide targeted patch guidance instead of broad rewrites.
+
+## Outputs to provide
+- Minimal integration diff (exact files and snippets).
+- Verification checklist (build, check update, download, switch version).
+- Troubleshooting hints for common failures.
+
+## Resources
+- Read `references/integration-playbook.md` before giving steps.
+- Use `scripts/integration_doctor.sh` for quick project diagnosis.

skill/react-native-update/SKILL.md

@@ -0,0 +1,56 @@
+# react-native-update integration playbook
+
+## 1) Fast path
+1. Install CLI and SDK in app root:
+   - `npm i -g react-native-update-cli`
+   - `npm i react-native-update`
+2. iOS pod install:
+   - `cd ios && pod install`
+3. Generate/select app config (`update.json`) with pushy CLI.
+4. Wire appKey from `update.json` by platform.
+5. Initialize `Pushy` and wrap app with `UpdateProvider`.
+6. Build release package and validate update flow.
+
+## 2) App type specifics
+
+### React Native CLI
+- Standard install + iOS pods.
+- For very old RN or non-standard project structure, manual link may still be needed.
+
+### Expo
+- Require modern Expo workflow; run prebuild when needed:
+  - `npx expo prebuild`
+- Do not co-install `expo-updates` (conflict risk for update behavior).
+
+## 3) Minimum JS wiring
+- Read appKey from `update.json` with `Platform.OS`.
+- Create `new Pushy({ appKey, ...options })`.
+- Wrap app root with `<UpdateProvider client={pushyClient}>`.
+
+## 4) Strategy defaults to discuss
+- `checkStrategy`: `both` / `onAppStart` / `onAppResume` / `null`
+- `updateStrategy`: `alwaysAlert` / `alertUpdateAndIgnoreError` / `silentAndNow` / `silentAndLater` / `null`
+- For custom UI: set `updateStrategy: null`, then use `useUpdate()`.
+
+## 5) Native touchpoints (high level)
+
+### iOS
+- Ensure release bundle URL resolves via Pushy bundle method in app delegate flow.
+- Keep DEBUG bundle behavior unchanged.
+
+### Android
+- Ensure integration point in `MainApplication` (or custom React instance manager path).
+
+## 6) Verification checklist
+- [ ] Release build succeeds on target platform.
+- [ ] App can call check update and returns structured update state.
+- [ ] Update package download succeeds.
+- [ ] App can switch to new version (now/later behavior as expected).
+- [ ] Rollback behavior understood/tested for crash scenarios.
+
+## 7) Common pitfalls
+- Missing/incorrect `update.json` appKey by platform.
+- Expecting real apply-update behavior in DEBUG builds.
+- Expo project still carrying `expo-updates`.
+- iOS pods not installed after dependency update.
+- Native file edits not followed by full rebuild.

skill/react-native-update/references/integration-playbook.md

@@ -0,0 +1,53 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+APP_ROOT="${1:-$(pwd)}"
+cd "$APP_ROOT"
+
+echo "[doctor] app root: $APP_ROOT"
+
+ok(){ echo "[ok] $*"; }
+warn(){ echo "[warn] $*"; }
+miss(){ echo "[missing] $*"; }
+
+if [ -f package.json ]; then
+  ok "package.json found"
+else
+  miss "package.json not found"
+  exit 2
+fi
+
+if node -e "const p=require('./package.json'); process.exit((p.dependencies&&p.dependencies['react-native-update'])||(p.devDependencies&&p.devDependencies['react-native-update'])?0:1)"; then
+  ok "react-native-update dependency present"
+else
+  miss "react-native-update dependency missing"
+fi
+
+if [ -f update.json ]; then
+  ok "update.json found"
+  if node -e "const u=require('./update.json'); const good=(u.ios&&u.ios.appKey)||(u.android&&u.android.appKey); process.exit(good?0:1)"; then
+    ok "update.json includes platform appKey"
+  else
+    warn "update.json exists but appKey looks incomplete"
+  fi
+else
+  miss "update.json missing (run pushy createApp/selectApp)"
+fi
+
+if [ -d ios ]; then
+  if [ -f ios/Podfile ]; then
+    ok "ios/Podfile found"
+  else
+    warn "ios exists but Podfile missing"
+  fi
+fi
+
+if [ -d android ]; then
+  ok "android project found"
+fi
+
+if grep -R --line-number --include='package.json' 'expo-updates' . >/dev/null 2>&1; then
+  warn "expo-updates detected; may conflict depending on integration mode"
+fi
+
+echo "[doctor] done"