Back to Details

react-native-update

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

React Native Update Integration

React Native Update集成

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.
使用本技能可将项目从「未集成」状态推进至「Release包中热更新可正常运行」状态。优先提供可安全复制粘贴的操作步骤、最小可行改动，以及明确的验证检查节点。

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.
  1. 检测应用类型（React Native CLI 还是 Expo）和目标平台。
  2. 执行
    references/integration-playbook.md
    中的依赖/安装步骤。
  3. 配置所需的原生设置（Bundle URL / MainApplication 集成点）。
  4. 添加
    Pushy
    客户端 + 
    UpdateProvider
    最小启动逻辑。
  5. 运行
    scripts/integration_doctor.sh <app-root>
    检测常见遗漏项。
  6. 返回简短的操作列表：已完成/待补充/下一步验证。

Platform routing

平台适配路由

  • If user context is OpenClaw: provide OpenClaw-first instructions and file/workspace conventions.
  • If user context is Claude Code: provide Claude Code-first command style and workflow wording.
  • If context is unknown: provide neutral steps first, then append OpenClaw/Claude Code notes.
  • Keep technical steps identical; only adapt command conventions and delivery style.
  • 如果用户上下文是OpenClaw：优先提供OpenClaw适配的操作指引、文件/工作区规范。
  • 如果用户上下文是Claude Code：优先提供符合Claude Code风格的命令格式和工作流表述。
  • 如果上下文未知：先提供中立步骤，再附加OpenClaw/Claude Code相关说明。
  • 技术步骤保持完全一致，仅调整命令规范和交付风格。

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.
  • 尽量减少用户的代码改动，且改动范围要局部化。
  • 不要承诺热更新在Debug模式下可正常运行，强调必须在Release包下验证。
  • 针对Expo项目，需提醒
    expo-updates
    冲突问题。
  • 保留现有应用架构，代码片段要适配当前项目的风格。
  • 如果原生文件差异极大（monorepo/混合原生项目），提供针对性的补丁指引，而非大范围重写。

Outputs to provide

需要交付的产出

  • Minimal integration diff (exact files and snippets).
  • Verification checklist (build, check update, download, switch version).
  • Troubleshooting hints for common failures.
  • Scenario examples when requested (including class component integration and custom whitelist rollout).
  • 最小集成diff（精确到文件和代码片段）。
  • 验证检查清单（构建、检查更新、下载、切换版本）。
  • 常见故障的排查提示。
  • 按需提供场景示例（包括类组件集成、自定义白名单灰度发布）。

Resources

参考资源

  • Read 
    references/integration-playbook.md
    before giving steps.
  • Use 
    scripts/integration_doctor.sh
    for quick project diagnosis.
  • 给出步骤前请先阅读
    references/integration-playbook.md
    。
  • 使用
    scripts/integration_doctor.sh
    对项目进行快速诊断。