Token导航 LogoToken导航TokenDH.com
运维和基础设施执行命令github未标认证来源可访问clear审计未展示

creating-upgrade-test-version创建升级测试版本

Agent Skill

用于辅助测试设计、自动化测试、用例整理和回归验证。它适合让 Agent 编写单元测试、端到端测试、测试计划或根据失败日志定位问题。使用时需要确认项目测试框架、运行命令和夹具数据,避免为了通过测试而改坏真实逻辑;涉及浏览器或外部服务时,应区分本地模拟、测试环境和生产环境。

总安装

297

周安装

12

GitHub Stars

2,417

下载量

93
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

3

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:creating-upgrade-test-version(创建升级测试版本)
来源仓库:https://github.com/onekeyhq/app-monorepo
仓库路径:skills/creating-upgrade-test-version
安装命令:
npx skills add https://github.com/onekeyhq/app-monorepo --skill creating-upgrade-test-version
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/onekeyhq/app-monorepo --skill creating-upgrade-test-version

简介

creating-upgrade-test-version 用于自动化创建带硬编码构建配置的测试版本分支。

  • 支持应用升级测试与版本迁移流验证,适用于持续交付场景。
  • 需用户提供测试版本号并按格式 9XXX.YY.Z 计算构建编号。
  • 涉及生产环境模拟时应区分测试环境与真实部署边界。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Creating Upgrade Test Version

Automates the creation of test version branches with hardcoded build configurations for testing app upgrade functionality and version migration flows.

Workflow

Step 1: Gather Version Information

Ask the user for the test version number using AskUserQuestion:

Question: "What test version number should be used?"
Options:
- "9005.20.0" (example format)
- Custom input

The version should follow the pattern 9XXX.YY.Z where:

  • 9XXX indicates a test version (e.g., 9005)
  • YY.Z matches the production version being tested

Step 2: Calculate Build Number

Calculate the build number as: current date (YYYYMMDD) + "00" suffix + 30

The build number must be 10 digits in format: YYYYMMDD00 + 30 = YYYYMMDD30

Example: If today is 20260113, the build number is 2026011300 + 30 = 2026011330

# Calculate build number (10 digits)
DATE=$(date +%Y%m%d)
BUILD_NUMBER=$((${DATE}00 + 30))
echo "Build number: $BUILD_NUMBER"  # Output: 2026011330

Step 3: Create and Checkout Branch

Create a new branch named after the test version:

git checkout -b <test_version>
# Example: git checkout -b 9005.20.0

Step 4: Modify Configuration Files

Modify the following files in order:

4.1 Update .env.version

Change the VERSION field to the test version:

VERSION=<test_version>
BUNDLE_VERSION=1

4.2 Update .github/actions/shared-env/action.yml

In the "Setup ENV BUILD_NUMBER" steps, replace ALL build number logic with a hardcoded value. Remove the if/else conditions and simplify to:

- name: Setup ENV BUILD_NUMBER
  shell: bash
  run: |
    echo "BUILD_NUMBER=<calculated_build_number>" >> $GITHUB_ENV

Remove both:

  • "Setup ENV BUILD_NUMBER to 1" step
  • "Setup ENV BUILD_NUMBER by workflow_run" step

Replace with single step that hardcodes the build number.

4.3 Update .github/workflows/release-android.yml

In the "Write.env.version" step, change:

echo "BUILD_NUMBER=${{ env.BUILD_NUMBER }}" >> .env.version

To:

echo "BUILD_NUMBER=<calculated_build_number>" >> .env.version

4.4 Update apps/mobile/android/app/build.gradle

In the defaultConfig block, update:

versionCode <calculated_build_number>
versionName "<test_version>"

Example:

versionCode 2026011330
versionName "9005.20.0"

Step 5: Commit and Push

git add -A
git commit -m "chore: prepare test version <test_version> with build number <build_number>"
git push -u origin <test_version>

File Locations Summary

FileChange
.env.versionUpdate VERSION
.github/actions/shared-env/action.ymlHardcode BUILD_NUMBER, remove conditionals
.github/workflows/release-android.ymlHardcode BUILD_NUMBER in.env.version write
apps/mobile/android/app/build.gradleUpdate versionCode and versionName

Example Execution

For test version 9005.20.0 on date 2026-01-13:

  1. Build number = 2026011300 + 30 = 2026011330 (10 digits)
  2. Create branch 9005.20.0
  3. Set VERSION=9005.20.0 in .env.version
  4. Hardcode BUILD_NUMBER=2026011330 in shared-env action
  5. Hardcode BUILD_NUMBER=2026011330 in release-android workflow
  6. Set versionCode=2026011330, versionName="9005.20.0" in build.gradle
  7. Commit and push

Validation Checklist

Before pushing, verify:

  • Branch name matches test version
  • .env.version VERSION field updated
  • Build number conditionals removed from shared-env
  • Build number hardcoded in release-android workflow
  • versionCode is numeric (build number)
  • versionName is quoted string (test version)

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Claude Code

29.86%
按下载量换算28

Gemini CLI

19.69%
按下载量换算18

Antigravity

15.58%
按下载量换算14

OpenCode

13.2%
按下载量换算12

Codex

7.04%
按下载量换算7

github-copilot

3.67%
按下载量换算3

安全审计

暂无安全审计结果可展示。

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/onekeyhq/app-monorepo --skill creating-upgrade-test-version;npx skills add onekeyhq/app-monorepo --skill "creating-upgrade-test-version" 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。

来源信息

继续浏览同类 Skills