What problem does it solve? Releasing a new version of the Agentero app requires updating version numbers scattered across many files (package.json, tauri.conf.json, multiple Cargo.toml files, iOS project config). Manually editing each one is error-prone and can produce mismatched versions between the desktop installer, CLI, and release tag. ## Core Features & Use Cases - Unified Version Sync: Updates the version field in package.json, src-tauri/tauri.conf.json, src-tauri/Cargo.toml, crates/agentero-core/Cargo.toml, cli/Cargo.toml, and the iOS CFBundleShortVersionString/CFBundleVersion in one pass. - SemVer Validation: Verifies the target version is a valid SemVer string and stops to ask for clarification when the version argument is missing or ambiguous. - Release Safety Checks: Confirms Cargo.lock no longer holds stale local package versions, that agentero --version still derives from the CLI package version, and that release documentation rules remain consistent. - Use Case: When preparing release 0.1.3, invoke this Skill so every manifest is bumped together, minimal verification commands run, and you get a summary of changed files before creating the v0.1.3 tag. ## Quick Start Ask the agent to bump the project version to 0.1.3 using the bump skill and report the modified files and verification results.