hot-updater

name	hot-updater
description	Use when working with Hot Updater CLI setup, deployment, bundle inventory, bundle enable/disable, rollback, channels, database migration, diagnostics, or AI-assisted React Native OTA operations.
metadata	{"author":"hot-updater","version":"1.0.0"}

Hot Updater CLI

Use this skill when a task involves Hot Updater's CLI, hot-updater.config.ts, React Native OTA deployment, bundle operations, rollback, or release-channel management.

Operating Rules

• Start from the project root unless the user specifies another app directory.
• Read local hot-updater.config.ts before assuming provider behavior.
• Use npx hot-updater ... for CLI examples and user-facing instructions.
• Do not run npx hot-updater init on behalf of the user. It is interactive and asks for provider, build, and project-specific choices. Guide the user to run it directly and follow the setup documentation.
• Before running npx hot-updater doctor, make sure the server base URL is available. If the user did not provide it and it is not obvious from local config, ask for the update server URL first.
• Treat deploy, bundle enable, bundle disable, rollback, and database migration as state-changing operations.
• Use --json only with read-only commands documented here as supporting it; if a target project uses an older CLI without that option, fall back to the human-readable output.
• For non-interactive shells, use -y only when the user already requested the exact mutation or the target is unambiguous.
• After mutating bundle state, verify with bundle list or the relevant provider state.
• If deploy fails, stop the deploy workflow. Do not keep retrying fixes, edit setup, change credentials, install dependencies, or run migrations unless the user explicitly asks for that follow-up. Analyze only the failed command, relevant output, likely cause, and suggested next checks.
• Do not edit provider credentials unless the user explicitly asks. Credentials are commonly stored in .env.hotupdater, but projects may use a different environment-loading setup.

Natural Language Requests

Users may invoke this skill with prompts such as:

$hot-updater deploy using the current app version
$hot-updater deploy the current iOS app version to production
$hot-updater roll back the most recently deployed bundle
$hot-updater list iOS bundles on the production channel
$hot-updater run doctor with server URL https://updates.example.com/api/check-update

Translate the request into the safest CLI flow. If a state-changing request is missing a required platform, bundle target, or server URL that cannot be inferred from local context, ask one concise question before mutating anything. For deploy channel, use the CLI default production unless the user names another channel or local context clearly indicates one.

Current App Version Deploy

When the user asks to deploy for the current app version:

1. Run npx hot-updater app-version --json when supported; otherwise run npx hot-updater app-version.
2. Extract ios and/or android from JSON when available, or from the human-readable output as a fallback.
3. If the platform is missing, ask whether to deploy iOS, Android, or both.
4. Deploy with -t <version>:

npx hot-updater deploy -p ios -t <ios-app-version>
npx hot-updater deploy -p android -t <android-app-version>

If deploying both platforms, run one platform at a time and verify each result with npx hot-updater bundle list -p <platform> --limit 5 --json when supported, or without --json as a fallback.

If a deploy command fails, do not continue to the next platform or attempt an automatic repair. Report the failure analysis and wait for a new user request.

Recent Bundle Rollback

When the user asks to roll back the most recent deployment without naming a bundle:

1. Run npx hot-updater bundle list --json --limit 10.
2. Choose the most recent enabled bundle from the JSON result.
3. Use that bundle's channel, platform, and id for a scoped rollback:

npx hot-updater rollback <channel> -p <platform> --target <bundle-id> -y

If the most recent bundle is already disabled, tell the user and ask whether to roll back the next enabled bundle. After rollback, verify with:

npx hot-updater bundle list -c <channel> -p <platform> --limit 5 --json

If --json is unavailable, rerun the same command without --json.

Core Commands

Setup and Diagnostics

npx hot-updater init
npx hot-updater doctor --server-base-url <update-server-url>
npx hot-updater app-version
npx hot-updater app-version --json
npx hot-updater console

• init creates or updates project configuration. Because it is interactive, tell the user to run it directly instead of choosing answers for them.
• doctor checks local setup and server health. Provide --server-base-url; if the user has not provided one, ask for it before running the command.
• app-version reads native iOS and Android app versions. --json returns { "android": string | null, "ios": string | null } on CLIs that support it.
• console opens the local management console.

Deploy

npx hot-updater deploy -p <ios|android>
npx hot-updater deploy -p ios -c production -r 25
npx hot-updater deploy -p android -f
npx hot-updater deploy -p ios -d

Important options:

Option	Meaning
-p, --platform <platform>	Target ios or android.
-c, --channel <channel>	Release channel, default production.
-t, --target-app-version <range>	App version range such as 1.2.3 or 1.x.x.
-r, --rollout <percentage>	Initial rollout percentage from 0 to 100.
-f, --force-update	Apply immediately on client update.
-d, --disabled	Upload disabled for later enablement.
-m, --message <message>	Custom deployment message.
-i, --interactive	Guided deployment flow.

Bundle Inventory and State

npx hot-updater bundle list
npx hot-updater bundle list -c production -p ios --limit 10
npx hot-updater bundle list -c production -p ios --limit 10 --json
npx hot-updater bundle list --json
npx hot-updater bundle disable <bundle-id>
npx hot-updater bundle enable <bundle-id>

• bundle list shows the most recent bundles first.
• --json is available for raw bundle data on CLIs that support it.
• bundle disable and bundle enable read the bundle, mutate enabled state, commit the change, then re-read to verify.
• In CI or other non-interactive shells, pass -y to enable or disable.

Rollback

npx hot-updater rollback <channel>
npx hot-updater rollback production -p ios
npx hot-updater rollback production -p ios --target <bundle-id> -y

• Rollback disables the latest enabled bundle on the channel.
• Without -p, rollback applies to both iOS and Android.
• The next most recent enabled bundle on the same channel and platform becomes the fallback.
• If no previous enabled bundle exists, the app falls back to the JavaScript bundle shipped in the native binary.
• Use --target <bundle-id> to retry a partial rollback for exactly one bundle.

Channels

npx hot-updater channel set <channel>

This writes the default channel into native iOS and Android project files. Changing this embedded channel requires a native rebuild.

Database

npx hot-updater db generate
npx hot-updater db migrate

• db generate creates migration output without applying it.
• db migrate applies the latest migration through the configured database plugin.