Agent skill

AionUi Version Bump

Automates an AionUi release: checks the latest AionCore release and its artifacts, updates package.json, writes the changelog, opens a PR and tags the release.

Apache-2.0Auto-check passedDevelopment

Install AionUi Version Bump

skills CLI

$ npx skills add iOfficeAI/AionUi --skill bump-version -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install iOfficeAI/AionUi bump-version --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/iOfficeAI/AionUi.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/bump-version .claude/skills/bump-version && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "bump-version" agent skill from https://github.com/iOfficeAI/AionUi/tree/main/.claude/skills/bump-version into .claude/skills/bump-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-version", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/iOfficeAI/AionUi/tree/main/.claude/skills/bump-version

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add iOfficeAI/AionUi --skill bump-version -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install iOfficeAI/AionUi bump-version --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iOfficeAI/AionUi.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/bump-version .agents/skills/bump-version && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "bump-version" agent skill from https://github.com/iOfficeAI/AionUi/tree/main/.claude/skills/bump-version into .agents/skills/bump-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-version", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add iOfficeAI/AionUi --skill bump-version -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install iOfficeAI/AionUi bump-version --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iOfficeAI/AionUi.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/bump-version .cursor/skills/bump-version && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "bump-version" agent skill from https://github.com/iOfficeAI/AionUi/tree/main/.claude/skills/bump-version into .cursor/skills/bump-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-version", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/iOfficeAI/AionUi.git --path .claude/skills/bump-version

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add iOfficeAI/AionUi --skill bump-version -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install iOfficeAI/AionUi bump-version --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iOfficeAI/AionUi.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/bump-version .gemini/skills/bump-version && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "bump-version" agent skill from https://github.com/iOfficeAI/AionUi/tree/main/.claude/skills/bump-version into .gemini/skills/bump-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-version", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install iOfficeAI/AionUi bump-version

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add iOfficeAI/AionUi --skill bump-version -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/iOfficeAI/AionUi.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/bump-version .github/skills/bump-version && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "bump-version" agent skill from https://github.com/iOfficeAI/AionUi/tree/main/.claude/skills/bump-version into .github/skills/bump-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-version", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add iOfficeAI/AionUi --skill bump-version -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install iOfficeAI/AionUi bump-version --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/iOfficeAI/AionUi.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/bump-version .opencode/skills/bump-version && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "bump-version" agent skill from https://github.com/iOfficeAI/AionUi/tree/main/.claude/skills/bump-version into .opencode/skills/bump-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-version", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: bump-version
GitHub stars: 33k
Token cost: ~2.1k tokens
SKILL.md length: 632 words
Files: 1
Skills in repo: 4
Repo updated: Sep 9, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Automates an AionUi release: checks the latest AionCore release and its artifacts, updates package.json, writes the changelog, opens a PR and tags the release.

Works in 12 steps: Pre-flight Checks → Pull Latest → Determine AionUi Target Version → …
Preparing a new AionUi release
SKILL.md covers Workflow and Quick Reference
Calls git, gh and bun; reaches github.com

What it does

The skill is a slash command, /bump-version, that takes an optional AionUi version and flags such as --core to pin an AionCore tag or --skip-core for a frontend-only release. It starts with pre-flight checks: the agent must be on main with a clean working tree, then pulls the latest code with git pull --rebase, stopping with a clear message if any of that fails. Without a version argument it raises the patch number by one.

Unless --skip-core is set, it queries the latest AionCore release with gh release view, shows the version for you to confirm and warns when package.json already holds it. It then verifies that the 7 expected release assets exist, covering x86_64 and aarch64 builds for Linux, macOS and Windows plus a checksums file, and stops if any are missing. Next it edits the version and aioncoreVersion fields in package.json. Later steps generate a CHANGELOG, create a branch, commit and push, open a pull request, auto-merge it and tag the release.

When your agent uses it

Preparing a new AionUi release
Updating the pinned AionCore version in package.json
Cutting a frontend-only release without touching the core version

Example prompts

“Bump the AionUi version to the next patch release using the latest AionCore.”
“Bump AionUi to 2.2.0 and pin AionCore to v0.1.12.”
“Run bump-version for a frontend-only release and skip the AionCore update.”

Requirements

GitHub CLI (gh), authenticated
Git, on a clean main branch

Workflow steps

12 steps, taken from the step headings in SKILL.md.

Pre-flight Checks
Pull Latest
Determine AionUi Target Version
Query AionCore Latest Release
Verify AionCore Artifacts
Update package.json
Generate CHANGELOG Entry
Quality Checks
Run Tests
Branch, Commit, Push
Create PR + Enable Auto-Merge
Poll for Merge

What it can do on your machine

Read from SKILL.md and the folder at commit 6744099. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
- gh
- bun
- bunx
- just
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

AionUi Version Bump loads about 2.1k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 632 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~48
When it runs · the whole SKILL.md, loaded when a task matches: ~2.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from iOfficeAI/AionUi at commit 6744099, republished under its Apache-2.0 licence (© iOfficeAI). 632 words, ~2,058 tokens.

Download SKILL.mdSave it as .claude/skills/bump-version/SKILL.md (or your agent's skills folder).

name: bump-version
description: Use when bumping the AionUi version: query AionCore release, verify artifacts, update package.json, generate CHANGELOG, branch, commit, push, create PR, auto-merge, tag release.

Bump Version

Automate the AionUi release preparation: query AionCore release → verify artifacts → update versions → generate CHANGELOG → branch → PR → tag.

Usage: /bump-version [version] [flags]

/bump-version — auto patch + latest AionCore
/bump-version 2.2.0 — explicit AionUi version + latest AionCore
/bump-version 2.2.0 --core v0.1.12 — explicit both versions
/bump-version --skip-core — pure frontend release (don't touch aioncoreVersion)

Workflow

Step 1: Pre-flight Checks

bash

git branch --show-current
git status --short

Not on main → Stop: "Please switch to main before running bump-version."
Dirty working tree → Stop: "There are uncommitted changes. Please commit or stash them first."

Step 2: Pull Latest

bash

git pull --rebase origin main

Fails → Stop: "Failed to pull latest code. Please resolve conflicts or network issues first."

Step 3: Determine AionUi Target Version

Read package.json → extract version field.

Argument provided → use as-is
No argument → parse major.minor.patch, increment patch by 1

Display: "Bumping AionUi: {current} → {target}"

Step 4: Query AionCore Latest Release

Skip entirely if --skip-core is set.

bash

gh release view --repo iOfficeAI/AionCore --json tagName,body

If --core <version> provided → use that tag instead of latest
Display the AionCore version and ask user to confirm before continuing
Also read current aioncoreVersion from package.json — if it already matches the queried version, warn the user and ask whether to proceed or use --skip-core

Step 5: Verify AionCore Artifacts

Skip if --skip-core.

bash

gh release view <tag> --repo iOfficeAI/AionCore --json assets --jq '.assets[].name'

Verify all 7 expected assets exist:

aioncore-<tag>-x86_64-unknown-linux-gnu.tar.gz
aioncore-<tag>-aarch64-unknown-linux-gnu.tar.gz
aioncore-<tag>-x86_64-apple-darwin.tar.gz
aioncore-<tag>-aarch64-apple-darwin.tar.gz
aioncore-<tag>-x86_64-pc-windows-msvc.zip
aioncore-<tag>-aarch64-pc-windows-msvc.zip
aioncore-checksums.txt

Missing → Stop: "AionCore {tag} is missing artifacts: {list}. Wait for CI to complete or check for build failures."

Step 6: Update package.json

Use Edit tool to replace:

"version": "{current}" → "version": "{target}"
"aioncoreVersion": "{old}" → "aioncoreVersion": "{new core tag}" (skip if --skip-core)

Step 7: Generate CHANGELOG Entry

7a: Determine Previous Tag

bash

git describe --tags --abbrev=0

This gives the most recent tag (e.g. v2.1.2).

7b: Collect Frontend Changes

bash

git log v{previous}..HEAD --oneline --no-merges --format="%s"

Filter to conventional commit types: feat, fix, refactor, perf, style
Exclude commits matching chore: bump version
Group by type (Features, Bug Fixes, Refactoring, Performance, Styling)
Format each as: - **scope:** description (#PR)

7c: Collect AionCore Changes

From step 4's release body (already in conventional-changelog format from release-please). Parse into same grouped format.

Skip if --skip-core.

7d: Compose and Write CHANGELOG.md

If CHANGELOG.md exists at repo root → read its current content. If not → start with empty string.

Prepend the new entry in this format:

markdown

# Changelog

## [{target}](https://github.com/iOfficeAI/AionUi/compare/v{previous}...v{target}) ({date YYYY-MM-DD})

### Desktop

#### Bug Fixes

- **upload:** abort in-flight uploads when switching conversations (#3019)

#### Features

- **thinking:** add streaming indicator (#3015)

### Core ([{core tag}](https://github.com/iOfficeAI/AionCore/releases/tag/{core tag}))

#### Bug Fixes

- **acp:** load user MCP servers and emit empty-finish diagnostic (#327)

---

Rules:

If --skip-core: omit the entire "### Core" section
If no frontend commits since last tag: show _No frontend changes in this release._ under "### Desktop"
Date format: YYYY-MM-DD
Always keep the top-level # Changelog header exactly once

Show full SKILL.md (250 more words)Show less

Step 8: Quality Checks

bash

bun run lint
bun run format
bunx tsc --noEmit

lint fails → Stop: "Lint errors found. Please fix them before bumping."
format → Auto-fixes silently.
tsc fails → Stop: "TypeScript errors found. Please fix them before bumping."

Step 9: Run Tests

bash

bunx vitest run

Fails → Stop: "Tests failed. Please fix before bumping."

Step 10: Branch, Commit, Push

bash

git checkout -b chore/bump-version-{target}
git add package.json CHANGELOG.md
git commit -m "chore: bump version to {target} and aioncore to {core tag}"
just push -u origin chore/bump-version-{target}

If --skip-core:

bash

git commit -m "chore: bump version to {target}"

Step 11: Create PR + Enable Auto-Merge

bash

gh pr create --base main \
  --title "chore: bump version to {target}" \
  --body "<the CHANGELOG entry generated in Step 7>"

Capture the PR number from the output. Then enable auto-merge (squash):

bash

gh pr merge {PR_NUMBER} --auto --squash

Display: "PR created: {URL}. Auto-merge enabled — will merge automatically once CI passes."

Step 12: Poll for Merge

Check PR merge status every 5 minutes:

bash

gh pr view {PR_NUMBER} --json state,mergedAt,mergeStateStatus

Decision logic:

`state`	Action
`MERGED`	Proceed to Step 13
`CLOSED` (not merged)	Stop: "PR was closed without merging. Please check and confirm how to proceed."
`OPEN` with `mergeStateStatus: BLOCKED` or CI failure persisting > 3 checks	Stop: "PR merge is blocked (CI failure or review required). Please investigate: {URL}"
`OPEN` otherwise	Wait 5 minutes, check again

Maximum wait: 30 minutes (6 checks). If not merged after 30 minutes:

"PR has not merged after 30 minutes. Please check status: {URL}. Reply 'continue' when merged, or 'abort' to stop."

Wait for user confirmation only in this timeout case.

Step 13: Cleanup + Tag

After merge is confirmed (either via polling or user confirmation):

bash

git checkout main
git pull --rebase origin main
git branch -d chore/bump-version-{target}

Check if remote branch still exists:

bash

git ls-remote --heads origin chore/bump-version-{target}

Has output → git push origin --delete chore/bump-version-{target}
No output → skip

Create and push tag:

bash

git tag v{target}
git push origin v{target}

Wait a few seconds for GitHub to pick up the tag push, then fetch the triggered workflow run:

bash

gh run list --workflow=release.yml --branch v{target} --limit 1 --json databaseId,url

Display: "Tag v{target} created and pushed. Release build triggered! Action: {run URL}"

Quick Reference

 1. Must be on clean main
 2. git pull --rebase
 3. Determine AionUi target version (patch+1 or explicit)
 4. Query AionCore latest release (or --core / --skip-core)
 5. Verify AionCore artifacts (7 files)
 6. Edit package.json (version + aioncoreVersion)
 7. Generate CHANGELOG entry (frontend commits + AionCore release body)
 8. lint + format + tsc
 9. vitest run
10. branch → commit → push
11. gh pr create → enable auto-merge (squash)
12. poll merge status (every 5min, max 30min) → stop on failure
13. cleanup → git tag → git push tag

Files

Just SKILL.md in .claude/skills/bump-version of iOfficeAI/AionUi.

Open the folder on GitHubat commit 6744099

Compare with similar skills

AionUi Version Bump next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

AionUi Version Bump compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
AionUi Version Bump this skilliOfficeAI/AionUi	33k	—	~2.1k	Automated safety check: Pass	Apache-2.0	1 mo ago
ZCF Release AutomationUfoMiao/zcf	6.1k	—	~3.4k	Automated safety check: Pass	MIT	1 mo ago
Git Workflow and Versioningaddyosmani/agent-skills	103k	2 repos	~3.5k	Automated safety check: Notes	MIT	5 days ago
Verdaccio Pull Request Workflowverdaccio/verdaccio	18k	—	~1.9k	Automated safety check: Pass	MIT	today
Hunk Release Workflowmodem-dev/hunk	9.6k	—	~3.8k	Automated safety check: Pass	MIT	2 days ago
pybind11 Release Preparationpybind/pybind11	18k	—	~1.7k	Automated safety check: Pass	Custom licence	today

Similar skills

ZCF Release Automation
UfoMiao/zcf
Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.
6.1k GitHub stars~3.4k tokensUpdated 1 mo ago
DevelopmentAuto-check passed
Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
103k GitHub starsUsed in 2 repos~3.5k tokens
DevelopmentAuto-check: notes
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
18k GitHub stars~1.9k tokensUpdated today
DevelopmentAuto-check passed
Hunk Release Workflow
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
9.6k GitHub stars~3.8k tokensUpdated 2 days ago
DevelopmentAuto-check passed
pybind11 Release Preparation
pybind/pybind11
Opens the pybind11 release-preparation pull request: picking the release base, bumping the version in common.h and integrating the changelog, following docs/release.rst.
18k GitHub stars~1.7k tokensUpdated today
DevelopmentAuto-check passed
Git Changes Reporter
No-Trade-No-Life/Yuan
生成结构化 git 变更报告（JSON + Markdown）。使用此技能当用户提到"git 变更"、"commit 摘要"、"代码审查"、"release note"、"近期改动"、"每日摘要"，或需要分析指定 commit 区间的代码变更。包含三元组结构（设计意图、核心代码、影响范围）的语义化报告，适用于代码审查、发布说明、团队同步、CI/CD 等场景。
352 GitHub stars~1.2k tokensUpdated 5 mo ago
DevelopmentAuto-check passed

Questions about AionUi Version Bump

What does AionUi Version Bump do?

Automates an AionUi release: checks the latest AionCore release and its artifacts, updates package.json, writes the changelog, opens a PR and tags the release. The skill is a slash command, /bump-version, that takes an optional AionUi version and flags such as --core to pin an AionCore tag or --skip-core for a frontend-only release. It starts with pre-flight checks: the agent must be on main with a clean working tree, then pulls the latest code with git pull --rebase, stopping with a clear message if any of that fails.

When should I use AionUi Version Bump?

AionUi Version Bump fits situations like: preparing a new AionUi release; updating the pinned AionCore version in package.json; cutting a frontend-only release without touching the core version.

How do I install AionUi Version Bump in Claude Code?

Run `npx skills add iOfficeAI/AionUi --skill bump-version -a claude-code`. Or copy the skill folder (.claude/skills/bump-version in iOfficeAI/AionUi) into .claude/skills/bump-version in your project. Claude Code loads it when a task matches its description.

How do I install AionUi Version Bump in Codex?

Run `npx skills add iOfficeAI/AionUi --skill bump-version -a codex`. Or copy the skill folder (.claude/skills/bump-version in iOfficeAI/AionUi) into .agents/skills/bump-version in your project. Codex loads it when a task matches its description.

Can I use AionUi Version Bump in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add iOfficeAI/AionUi --skill bump-version -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bump-version, .gemini/skills/bump-version, .github/skills/bump-version and .opencode/skills/bump-version in your project.

What does AionUi Version Bump need to run?

Going by SKILL.md and its folder, AionUi Version Bump needs the command-line tools its instructions call (git, gh, bun, bunx and just). Our summary lists: GitHub CLI (gh), authenticated; Git, on a clean main branch.

Does AionUi Version Bump access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is AionUi Version Bump safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does AionUi Version Bump use?

AionUi Version Bump is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does AionUi Version Bump use?

About 2.1k tokens (SKILL.md is roughly 8.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to AionUi Version Bump?

Skills that share tags, products or a category with AionUi Version Bump: ZCF Release Automation (UfoMiao/zcf, 6.1k stars), Git Workflow and Versioning (addyosmani/agent-skills, 103k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars) and Hunk Release Workflow (modem-dev/hunk, 9.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains AionUi Version Bump?

iOfficeAI (a GitHub organization) maintains it in iOfficeAI/AionUi, which has 33,396 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on September 9, 2026.

Source: iOfficeAI/AionUi on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install AionUi Version Bump

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Bump Version

Workflow

Step 1: Pre-flight Checks

Step 2: Pull Latest

Step 3: Determine AionUi Target Version

Step 4: Query AionCore Latest Release

Step 5: Verify AionCore Artifacts

Step 6: Update package.json

Step 7: Generate CHANGELOG Entry

7a: Determine Previous Tag

7b: Collect Frontend Changes

7c: Collect AionCore Changes

7d: Compose and Write CHANGELOG.md

Step 8: Quality Checks

Step 9: Run Tests

Step 10: Branch, Commit, Push

Step 11: Create PR + Enable Auto-Merge

Step 12: Poll for Merge

Step 13: Cleanup + Tag

Quick Reference

Files

Compare with similar skills

Similar skills

More from iOfficeAI/AionUi

Related

Questions about AionUi Version Bump