What problem does it solve? Manually bumping HarmonyOS app versions is error-prone: versionCode must follow a YYMMDD plus daily build-sequence convention, stale version numbers linger across docs and source files, and unverified changes can ship wrong versions to devices. This Skill enforces a closed-loop workflow that updates, cleans, builds, installs, and verifies the new version. ## Core Features & Use Cases - Rule-based version computation: Generates versionCode as YYMMDD plus a two-digit daily build sequence (resetting across days, incrementing same-day) and bumps the patch digit of versionName. - Single source of truth: Edits only AppScope/app.json5, then greps the entire project (AGENTS.md, docs, feature contracts, .ets/.ts files) to zero out all references to the old version numbers. - Build-install-verify loop: Builds with dcli__build_project, installs the debug-signed HAP via dcli__install_hap, and confirms the new version on-device with hdc bm dump, avoiding the appQuickFix placeholder-field trap. - Use Case: Before releasing a new HarmonyOS build, ask the agent to bump the version; it computes today's sequence number, updates app.json5, clears stale references, installs the debug HAP, and verifies versionCode/versionName on the device. ## Quick Start Ask the agent to bump the HarmonyOS project version number and verify it on the connected device before release.