1k-app-upgrade-test
Create test versions to verify app auto-update functionality. Use when testing update flows, version migration, or validating app upgrade mechanisms. Automates version number and build number configuration for testing the auto-update system. Triggers on auto update, app upgrade, update testing, upgrade flow, version migration, test build, 9XXX version.
Best use case
1k-app-upgrade-test is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create test versions to verify app auto-update functionality. Use when testing update flows, version migration, or validating app upgrade mechanisms. Automates version number and build number configuration for testing the auto-update system. Triggers on auto update, app upgrade, update testing, upgrade flow, version migration, test build, 9XXX version.
Teams using 1k-app-upgrade-test should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/1k-app-upgrade-test/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How 1k-app-upgrade-test Compares
| Feature / Agent | 1k-app-upgrade-test | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create test versions to verify app auto-update functionality. Use when testing update flows, version migration, or validating app upgrade mechanisms. Automates version number and build number configuration for testing the auto-update system. Triggers on auto update, app upgrade, update testing, upgrade flow, version migration, test build, 9XXX version.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Test Version Creation
Automates creation of test version branches with hardcoded build configurations for testing app upgrade functionality and version migration flows.
## Quick Reference
### Version Pattern
Test versions follow the pattern: **`9XXX.YY.Z`**
- `9XXX` - Test version indicator (e.g., 9005)
- `YY.Z` - Matches production version being tested
Example: `9005.20.0` for testing production `5.20.0`
### Build Number Formula
Build number is calculated as:
```bash
DATE=$(date +%Y%m%d)
BUILD_NUMBER=$((${DATE}00 + 30))
```
**Format**: 10 digits = `YYYYMMDD00 + 30`
Example: If today is `20260130`, build number is `2026013030`
## Workflow
### Step 1: Get Version Information
Ask user for test version number:
- Format: `9XXX.YY.Z`
- Example: `9005.20.0`
### Step 2: Calculate Build Number
```bash
DATE=$(date +%Y%m%d)
BUILD_NUMBER=$((${DATE}00 + 30))
echo "Build number: $BUILD_NUMBER"
```
### Step 3: Create Branch
```bash
git checkout -b <test_version>
# Example: git checkout -b 9005.20.0
```
### Step 4: Modify Configuration Files
Update these files in order:
1. **`.env.version`**
- Set VERSION to test version
- Set BUILD_NUMBER to calculated value
2. **`.github/actions/shared-env/action.yml`**
- Update version in outputs section
3. **`.github/workflows/release-android.yml`**
- Update versionName in android-build job
4. **`apps/mobile/android/app/build.gradle`**
- Update versionCode
- Update versionName
### Step 5: Commit and Push
```bash
git add .
git commit -m "chore: create test version <version>"
git push origin <test_version>
```
## Files to Modify
| File | What to Update |
|------|----------------|
| `.env.version` | VERSION, BUILD_NUMBER |
| `.github/actions/shared-env/action.yml` | outputs.version |
| `.github/workflows/release-android.yml` | versionName |
| `apps/mobile/android/app/build.gradle` | versionCode, versionName |
## Detailed Guide
For comprehensive test version creation workflow with examples, see [upgrade-test-version.md](references/rules/upgrade-test-version.md).
Topics covered:
- Version number format and conventions
- Build number calculation formula
- Step-by-step file modification instructions
- Configuration file examples
- Git workflow for test versions
- QA testing considerations
## When to Use This Skill
- Creating test builds for QA upgrade testing
- Testing version migration flows
- Verifying app upgrade functionality
- Creating release candidates with specific build numbers
- Testing version-specific features or fixes
## Related Skills
- `/1k-git-workflow` - Git branching conventions
- `/1k-dev-commands` - Build and release commandsRelated Skills
add-unit-tests
Guide for adding unit tests to AReaL. Use when user wants to add tests for new functionality or increase test coverage.
add-test
Add unit tests for component or function: $ARGUMENTS
add-test-whatifwedigdeeper-application-tracker
Add unit tests for a component or function
add-test-coverage
Analyze recent changes and add test coverage for HEAD commit
add-backend-testing
Add backend integration testing with Vitest to an existing app. Sets up isolated test database schema and writes tests for tRPC routers.
adb-device-testing
Use when testing Android apps on ADB-connected devices/emulators - UI automation, screenshots, location spoofing, navigation, app management. Triggers on ADB, emulator, Android testing, location mock, UI test, screenshot walkthrough.
act-local-testing
Use when testing GitHub Actions workflows locally with act. Covers act CLI usage, Docker configuration, debugging workflows, and troubleshooting common issues when running workflows on your local machine.
accessibility-testing
WCAG 2.2 compliance testing, screen reader validation, and inclusive design verification. Use when ensuring legal compliance (ADA, Section 508), testing for disabilities, or building accessible applications for 1 billion disabled users globally.
accessibility-tester
Expert accessibility tester specializing in WCAG compliance, inclusive design, and universal access. Masters screen reader compatibility, keyboard navigation, and assistive technology integration with focus on creating barrier-free digital experiences.
accessibility-test-axe
Эксперт по a11y тестированию. Используй для axe-core, automated testing и accessibility audits.
acceptance-testing
Plan and (when feasible) implement or execute user acceptance tests (UAT) / end-to-end acceptance scenarios. Converts requirements or user stories into acceptance criteria, test cases, test data, and a sign-off checklist; suggests automation (Playwright/Cypress for web, golden/snapshot tests for CLIs/APIs). Use when validating user-visible behavior for a release, or mapping requirements to acceptance coverage.
acceptance-tester
Execute systematic acceptance testing to verify implementations against acceptance criteria. Use this skill when tasks mention "驗收測試", "acceptance testing", "驗收", "validate implementation", or when Gherkin scenarios need to be executed.