بنقرة واحدة
1k-app-upgrade-test
Create test versions to verify app auto-update functionality and version migration.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Create test versions to verify app auto-update functionality and version migration.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create or regenerate a patch-package patch in this monorepo. Use when you edit anything under node_modules/ and need a persisted .patch, or when `npx patch-package <pkg>` fails with "Couldn't find any versions for ... matches ^x@x". Keywords: patch-package, patch a package, regenerate patch, resolutions error.
App-side OneKey Trade/Swap/Market guide for Swap core, Swap Pro, Market speed-swap, K-line/chart, token selectors, cold-start frame-by-frame validation, quote/build/send flows, history/status, provider channels, PrivateSend-like channels, stock-trading channels, limit/order flows, fees, slippage, ETA, and cross-module funding handoffs.
Creates a Pull Request from current changes for OneKey app-monorepo. Use when user wants to create PR, submit changes, or merge feature branch. Handles branch creation, commit, push, and PR creation with conversation context extraction for code review AI.
AI-agent-driven UI verification for OneKey. Use to actually drive the running app and confirm a visual/interactive change works — Electron desktop via Chrome DevTools Protocol (CDP) on port 9222 with playwright-core, and React Native (iOS/Android) via callstack agent-device. Triggers on "verify the UI", "drive the app", "screenshot the change", "check it on desktop/simulator", "CDP 9222", "agent-device", "UI 验证", "跑一下看看", "截图确认".
App-side OneKey DeFi guide for Earn, Borrow, Staking, vaults, lending, protocol integrations, ABI-backed operations, native/provider-backed operations, pending transactions, history, route handoffs, risk display, and DeFi regression review.
Use only for explicit OneKey Perps/Hyperliquid (`views/Perp`, ServiceHyperLiquid, perpetuals, 永续/合约, Perps trading). Covers orderbook/L2/BBO, TWAP, scale/TIF/trigger/reduce-only, Perps TradingView/K-line, Perps Relay deposit, token selector, positions/account state/PnL/funding/margin/liquidation. Exclude generic Swap/Market/TradingView; Swap Relay quote/status/pending/requestId alone is not enough unless Perps deposit/Hyperliquid/`views/Perp`/`usePerpDeposit`/`fetchPerpDeposit*`/`perpsDepositOrderAtom` is explicit.
| name | 1k-app-upgrade-test |
| description | Create test versions to verify app auto-update functionality and version migration. |
| allowed-tools | Read, Grep, Glob, Write, Edit, Bash |
| disable-model-invocation | true |
Automates creation of test version branches with hardcoded build configurations for testing app upgrade functionality and version migration flows.
Test versions follow the pattern: 9XXX.YY.Z
9XXX - Test version indicator (e.g., 9005)YY.Z - Matches production version being testedExample: 9005.20.0 for testing production 5.20.0
Build number is calculated as:
DATE=$(date +%Y%m%d)
BUILD_NUMBER=$((${DATE}00 + 30))
Format: 10 digits = YYYYMMDD00 + 30
Example: If today is 20260130, build number is 2026013030
Ask user for test version number:
9XXX.YY.Z9005.20.0DATE=$(date +%Y%m%d)
BUILD_NUMBER=$((${DATE}00 + 30))
echo "Build number: $BUILD_NUMBER"
git checkout -b <test_version>
# Example: git checkout -b 9005.20.0
Update these files in order:
.env.version
.github/actions/shared-env/action.yml
.github/workflows/release-android.yml
.github/workflows/release-ios.yml
.github/workflows/daily-build.yml
apps/mobile/android/app/build.gradle
git add .
git commit -m "chore: create test version <version>"
git push origin <test_version>
| File | What to Update |
|---|---|
.env.version | VERSION |
.github/actions/shared-env/action.yml | Hardcode BUILD_NUMBER, remove conditionals |
.github/workflows/release-android.yml | Hardcode BUILD_NUMBER in .env.version write |
.github/workflows/release-ios.yml | Hardcode BUILD_NUMBER in .env.version write |
.github/workflows/daily-build.yml | Hardcode BUILD_NUMBER in Setup ENV step |
apps/mobile/android/app/build.gradle | versionCode, versionName |
For comprehensive test version creation workflow with examples, see upgrade-test-version.md.
Topics covered:
/1k-git-workflow - Git branching conventions/1k-dev-commands - Build and release commands