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.

16 stars

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

$curl -o ~/.claude/skills/1k-app-upgrade-test/SKILL.md --create-dirs "https://raw.githubusercontent.com/diegosouzapw/awesome-omni-skill/main/skills/development/1k-app-upgrade-test/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/1k-app-upgrade-test/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How 1k-app-upgrade-test Compares

Feature / Agent1k-app-upgrade-testStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/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 commands

Related Skills

test-tui

16
from diegosouzapw/awesome-omni-skill

Guide for testing Codex TUI interactively

test-pyramid-design

16
from diegosouzapw/awesome-omni-skill

Design optimal test pyramids with unit/integration/E2E ratios. Identify anti-patterns and recommend architecture-specific testing strategies.

dotnet-ui-testing-core

16
from diegosouzapw/awesome-omni-skill

Tests UI across frameworks. Page objects, test selectors, async waits, accessibility.

accessibility-testing

16
from diegosouzapw/awesome-omni-skill

Guide for conducting comprehensive accessibility audits of code to identify WCAG compliance issues and barriers to inclusive design. This skill should be used when reviewing accessibility, ARIA implementation, keyboard navigation, or screen reader compatibility.

repo-a-policy-selftest-gate

16
from diegosouzapw/awesome-omni-skill

Enforce Repo A DDC policy and acceptance gates before PRs. Use when changing policy files, node runtime behavior, guardrail-sensitive config, or validation tooling that must satisfy AGENTS.md acceptance commands.

rails-upgrade-assistant

16
from diegosouzapw/awesome-omni-skill

Analyzes Rails applications and generates comprehensive upgrade reports with breaking changes, deprecations, and step-by-step migration guides for Rails 7.0 through 8.1.1. Use when upgrading Rails applications, planning multi-hop upgrades, or querying version-specific changes.

minitest-testing

16
from diegosouzapw/awesome-omni-skill

Write, review, and improve Minitest tests for Ruby on Rails applications. Covers model tests, controller tests, system tests, fixtures, and best practices from Rails Testing Guide.

inference-smoke-tests

16
from diegosouzapw/awesome-omni-skill

Run repeatable inference smoke tests using geppetto/pinocchio example binaries (single-pass, streaming, tool-loop, OpenAI Responses thinking) including tmux-driven TUI tests. Use when refactors touch InferenceState/Session/EngineBuilder, tool calling loop, event sinks, provider request formatting, or when you need a quick 'does inference still work?' checklist.

ai-powered-pentesting

16
from diegosouzapw/awesome-omni-skill

Guide for AI-powered penetration testing tools, red teaming frameworks, and autonomous security agents.

Advanced Testability Ai Ergonomic

16
from diegosouzapw/awesome-omni-skill

Design code for testability and AI/LLM ergonomics with explicit contracts and observable patterns. Use when optimizing code for AI tools, improving testability, or making codebases LLM-friendly.

ab-testing-analyzer

16
from diegosouzapw/awesome-omni-skill

全面的AB测试分析工具,支持实验设计、统计检验、用户分群分析和可视化报告生成。用于分析产品改版、营销活动、功能优化等AB测试结果,提供统计显著性检验和深度洞察。

ab-test-framework-ml

16
from diegosouzapw/awesome-omni-skill

Эксперт A/B тестирования. Используй для статистических тестов, экспериментов и ML-оптимизации.