version-release

Name: version-release
Availability: InStock
Author: andershi666

Automate minor and patch releases with branch creation, PRs, and GitHub Releases.

1|Updated Apr 14, 2026

Search Tags:#automation #git #versioning #branching #release #ci

Ready to run

npx skills add https://github.com/andershi666/lobehub-hr-demo --skill version-release-andershi666

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: version-release
Source: https://github.com/andershi666/lobehub-hr-demo/tree/main/lobehub/.agents/skills/version-release
Command: npx skills add https://github.com/andershi666/lobehub-hr-demo --skill version-release-andershi666

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Version release workflow guidance for software teams, helping you manage minor and patch releases from canary to main with automated tagging and release creation.

Core Features & Use Cases

Minor Release Workflow: Create release branches from canary, determine version, and open PRs to main with a standardized title; after merge, auto-tag-release finalizes the release.
Patch Release Workflow: Auto bump patch +1 for weekly/hotfix scenarios and DB migrations; supports multiple branch naming patterns and CI-driven triggers.
Auto-Release Rules: Post-merge triggers based on PR title patterns or branch naming to determine Minor or Patch releases.
Post-Release Actions: Bump package.json, create annotated tag, generate GitHub Release, and sync main back to canary.
Claude Action Guide: Follow structured prompts to perform release planning and execution.

Quick Start

Create a release/v{version} branch from canary and open a PR to main with the title "🚀 release: v{version}".

Frequently Asked Questions about version-release

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

FAQPage Schema

How do I automate a minor version release from canary to main?▼

To automate a minor version release, create a release/v{version} branch from canary and open a PR to main titled "🚀 release: v{version}". Post-merge CI triggers automated tagging, package.json bumping, and GitHub Release generation.

What is the workflow for patch releases and hotfixes?▼

The patch release workflow auto-bumps the patch version +1 for weekly or hotfix scenarios and database migrations. It supports multiple branch naming patterns and CI-driven triggers to streamline hotfix deployment.

Can I use this to sync main back to canary after a release?▼

Yes, syncing main back to canary is a built-in post-release action. After the release branch merges into main and tagging completes, the workflow automatically syncs the updated main branch back to canary.

How does CI determine whether to trigger a minor or patch release?▼

CI determines the release type through post-merge auto-release rules based on PR title patterns or branch naming conventions. These rules distinguish between minor and patch releases to apply the correct versioning strategy.

What post-release actions are automatically performed after merging a release PR?▼

Post-release actions include bumping the package.json version, creating an annotated git tag, generating a GitHub Release, and syncing the main branch back to canary to complete the release cycle.

Do I need to follow specific branch naming conventions for versioning?▼

Yes, specific branch naming conventions like release/v{version} are required. The CI enforces versioning rules by matching branch names and PR title patterns to correctly identify and automate minor or patch releases.