메뉴
Create test versions to verify app auto-update functionality and version migration.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Analytics event tracking for OneKey. Use when adding tracking events, logging to server, user behavior tracking, or business metrics. Covers the @LogToServer decorator pattern, logger scope/scene architecture, and common pitfalls. Triggers on "埋点", "统计", "打点", "数据追踪", "日志", "analytics", "tracking event", "Mixpanel", "LogToServer", "trackEvent", "defaultLogger".
Release branch management — checkout from release, prepare builds, pre-release diff checks, publish tracking, and sync back to x. Use this skill when managing release branches, creating branches for bundle releases, running pre-release diff checks, finalizing releases, or syncing release changes to x. Triggers on "bundle release", "release diff", "release publish", "release sync", "release checkout", "发布管理", "release 分支", "release management", "bundle-release", "bundle branch".
Code quality standards — lint (eslint/oxlint), type check (tsc), pre-commit hooks, and comment conventions. All comments must be in English.
Comprehensive PR code review for OneKey monorepo. Use when reviewing PRs, code changes, or diffs — covers security (secrets/PII leakage, supply-chain, AuthN/AuthZ), code quality (hooks, race conditions, null safety, concurrent requests), and OneKey-specific patterns (Fabric crashes, MIUI, BigNumber). Triggers on "review PR", "review this PR", "code review", "check this diff", "审查 PR", "代码审查", "review
Coding patterns and best practices — React components, promise handling, and TypeScript conventions.
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.
| 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