skills.rest
gerald-ica
gerald-icaCOMMUNITY
Explore all skills by this author →
GitHub

bump-version

Bump the AionUi version in package.json and orchestrate release checks, branches, commits, PRs, and tags.

Updated Apr 14, 2026
Search Tags:#git#release#pr#ci-cd#lint#tests#version-bump
One-click install
npx skills add https://github.com/gerald-ica/opencode-config-snapshot --skill bump-version-gerald-ica
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bump-version
Source: https://github.com/gerald-ica/opencode-config-snapshot/tree/main/opencode/skills/bump-version
Command: npx skills add https://github.com/gerald-ica/opencode-config-snapshot --skill bump-version-gerald-ica

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end process of bumping the AionUi version in a repository, including updating package.json, running quality checks, managing branches, committing, pushing, creating a PR, and tagging the release.

Core Features & Use Cases

  • Automated version bump: Update the version in package.json and ensure consistency across config.
  • Workflow orchestration: Run lint, format, type checks, tests, and PR creation in a single flow.
  • Use Case: When releasing a new AionUi version, trigger the bump-version workflow to ensure a clean, auditable release process with proper metadata and tags.

Quick Start

Invoke the skill with a target version, e.g., bump-version 1.2.3, to perform an end-to-end release bump.

Frequently Asked Questions about bump-version

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a version bump in package.json end-to-end?▼

To automate a version bump end-to-end, this Skill updates the version in package.json, runs lint, format, and tsc checks, executes tests, and manages git branches, commits, PRs, and tags in a single coordinated flow.

What's the best way to coordinate git branches, commits, and tags during a release?▼

Coordinating git branches, commits, and tags during a release is handled by orchestrating branch naming, committing the updated package.json, pushing changes, creating a PR, and publishing a release tag through a single automated workflow command.

Can I run lint, type checks, and tests before creating a release PR?▼

Yes, you can run lint, format, and tsc type checks alongside tests before creating a release PR. This workflow orchestrates these quality checks sequentially and ensures they pass prior to opening the pull request.

Does this automated release workflow work in GitHub-like environments?▼

Yes, this automated release workflow works in GitHub-like environments, handling branch creation, PR creation, and tag publication natively across standard git and CI-CD release workflows.

Why should I use an automated version bump workflow instead of manual git operations?▼

Using an automated version bump workflow ensures a clean, auditable release process with proper metadata and tags, preventing human error during version parsing, package.json editing, and quality gate execution.

Related Skills

Explore More Software Engineering Skills→
hiddink-aihiddink-ai
1

hiddink-harness:npm-version

Automate npm package version bumps, changelogs, and git tags.

Official
Intermediate
Conceptual-MachinesConceptual-Machines
195

release

Create and push a v-prefixed git tag on the main branch.

Official
Intermediate
coreindustriescoreindustries
1

lint

Run linting, formatting, and type checks with auto-fix and strict mode.

Community
Intermediate
wollfoowollfoo

github-release-management

Automate GitHub release processes with versioning, testing, and deployment.

Community
Advanced