Bump Version — Automated Release Workflow for AionUi
One-command release automation: query AionCore release, verify artifacts, update package.json, generate CHANGELOG, create PR, auto-merge, and tag.
The skill performs many high-impact external operations (branching, committing, pushing, creating a PR with auto-merge, tagging) with incomplete user confirmation and excessive permissions: explicit confirmation is only requested when confirming the AionCore version and after the 30-minute poll timeout, while package.json changes, commits, pushes, and auto-merge are not confirmed. Data-flow transparency is moderate (uses gh commands), but handling of sensitive data (e.g., tokens) is not described. Source attribution is clear (Apache-2.0, pinned version), but publisher identity is unverified. Deductions: lack of user confirmation for high-risk actions, over-permission, unclear rollback.
Static review cannot execute paths, so max 10. Instructions are self-consistent and stepwise, but edge-case handling is weak: no handling of conflicting `--skip-core` and `--core`, CHANGELOG generation may fail on PR format, polling lacks detailed status for closed PRs, and failure messages are mostly 'Stop' without diagnostic depth. Dependencies like gh and bun are not checked. Deductions: unverified execution and incomplete error handling.
Scenario is clear: for AionUi maintainers to prepare releases. Boundaries are clear: stops on non-main branch, dirty tree, missing artifacts. Trigger conditions are listed in description, but variants like `--skip-core` are not in description, possibly causing false triggers. Environment fit: requires GitHub CLI and npm/bun, but no mention of mainland-China network reachability; GitHub access may be restricted, affecting usability. Scoring: clear scenario and boundaries, but network reachability unaddressed.
Documentation is well-structured with quick reference and stepwise instructions, easy to follow. Usage examples and flags are provided, but troubleshooting and known limitations are insufficient. Versioning, changelog, and update path are not declared in the skill doc, though repo has LICENSE and releases. Deductions: unclear maintenance responsibility and update path, missing troubleshooting and known limitations.
Static review cannot verify actual completion, so max 7. Skill design is complete, covering query to tagging, theoretically generating CHANGELOG, updating version, and triggering release build. But output is highly dependent on correct repo state, network, and authorization; CHANGELOG depends on git log and PR number format, may be inaccurate. High marginal value as automation of repetitive task, but no verification examples. Deductions: no execution evidence, output accuracy unverified.
Only source files, no third-party execution evidence. Max 5 but no CI workflows or test suites cover this skill, so give 2. Instructions are auditable but not independently verified. Deductions: no execution evidence, no test coverage.
- The skill involves high-risk operations (auto-merge PR, push tags) with incomplete user confirmation and permission control; review carefully and confirm critical steps manually before use.
- The skill depends on GitHub CLI and network access; mainland-China users may have unstable access to GitHub, affecting usability.
- Static review cannot verify actual execution; test in a small scope in a real environment first.
What does this skill do, and when should you use it?
This skill automates the entire release preparation for the AionUi repository through a 13-step workflow. It queries the latest AionCore release from GitHub and verifies all 7 expected build artifacts, then updates the local package.json version and aioncoreVersion fields, generates a CHANGELOG entry from git history and the AionCore release body, runs lint, format, TypeScript type-checking, and unit tests, creates a release branch and PR, enables squash auto-merge, polls for merge status, and finally cleans up branches and pushes a git tag to trigger a release build. It requires a clean main branch, GitHub CLI, and Bun. This skill is one of four bundled in the AionUi monorepo and focuses solely on version bumping, not on other collaborative features.
Executes a full release checklist: checks current git branch and working tree cleanliness; pulls the latest main; computes the target version from arguments or increments the patch version from package.json; queries AionCore's latest release via gh release view, supporting explicit --core version or --skip-core to bypass; verifies that 7 platform-specific artifact files and checksums exist in the AionCore release; edits package.json to update version and aioncoreVersion; runs git describe and git log to collect conventional commits and merges with AionCore release body to compose a CHANGELOG entry; runs bun run lint, bun run format, bunx tsc --noEmit, and bunx vitest run for quality gates; creates a branch, commits the changes, opens a PR with gh pr create, and enables squash auto-merge; polls PR merge status every 5 minutes (max 30 minutes), pausing for user confirmation on timeout; after merge, restores main, deletes local/remote branches, creates and pushes tag v{target}, and fetches the triggered release workflow run.
- AionUi maintainer wants to release a new patch version: run `/bump-version` and let the skill auto-increment the version and fetch latest AionCore, streamlining the release.
- A release requires specific versions: run `/bump-version 2.2.0 --core v0.1.12` to pin both AionUi and AionCore versions, preventing mismatches.
- AionCore is not ready, but a frontend fix must ship: use `/bump-version --skip-core` to skip AionCore-related steps and only bump the UI version.
- During CI failures or PR blocks, the skill halts and notifies the user, enabling manual inspection and intervention.
- After a merge timeout, the user can reply 'continue' or 'abort' to decide the next step, retaining control over the release process.
What are this skill's strengths and limitations?
- High automation, reducing a 13-step manual process to a single command, minimizing human error.
- Multiple safety checks: requires clean main, validates AionCore artifacts, runs lint/type/test gates, aborts on failure.
- Flexible version control with explicit or automated version selection.
- Full lifecycle closure: branch cleanup, tag push, and release workflow trigger after merge.
- User confirmation on timeout avoids blind automation in edge cases.
- Highly specific to the AionUi repo, with hard-coded AionCore repo name, artifact list, and release workflow; significant modification needed for other projects.
- Depends on GitHub CLI, Bun, and TypeScript; requires pre-configured environment.
- No built-in test suite or rollback; a failed step may leave orphan branches or PRs needing manual cleanup.
- Polling is capped at 30 minutes; longer CI runs may require manual intervention.
- GitHub-only; does not support other hosting platforms.
How do you install this skill?
- Clone the repository and checkout the main branch.
- Place the
.claude/skills/bump-version/folder inside the project's.claude/skills/directory (if using Claude Code). - Ensure GitHub CLI is installed and authenticated (
gh auth login), and that Bun is available (used for lint/format/tests). - The skill depends on the existing package.json, CHANGELOG.md, and the release.yml GitHub Actions workflow in the repo.
How do you use this skill?
Trigger the skill directly from Claude Code:
- /bump-version — auto patch version and use latest AionCore.
- /bump-version 2.2.0 — specify AionUi version, use latest AionCore.
- /bump-version 2.2.0 --core v0.1.12 — specify both versions.
- /bump-version --skip-core — pure frontend release.
Before running, ensure the working tree is clean and you are on main; the skill steps through the entire flow until completion or user intervention.