What problem does it solve? Preparing an AionUi release involves many error-prone manual steps: checking the AionCore release, verifying build artifacts, updating package.json, writing the CHANGELOG, running quality checks, creating a PR, waiting for merge, and tagging the release. This Skill automates the entire sequence with guardrails at each step. ## Core Features & Use Cases - End-to-End Release Automation: Queries the latest AionCore release, verifies all 7 platform artifacts exist, updates version and aioncoreVersion in package.json, and generates a grouped CHANGELOG entry from conventional commits. - Quality Gates: Runs lint, format, TypeScript checks, and vitest before committing, stopping immediately on any failure. - PR and Tag Management: Creates a release branch and PR, enables squash auto-merge, polls merge status for up to 30 minutes, then cleans up branches and pushes the version tag to trigger the release workflow. - Use Case: Run /bump-version 2.2.0 --core v0.1.12 to cut an explicit release, or /bump-version --skip-core for a pure frontend release without touching aioncoreVersion. ## Quick Start Ask the assistant to bump the AionUi version to the next patch release using the latest AionCore release.