Agent skill · software engineering · lobehub
version-release
Version release workflow — release process and GitHub Release notes (not docs/changelog pages).
Why this skill is useful
Adds specific CI/CD workflows and GitHub Release automation commands that the AI wouldn't reliably generate on its own.
What it needs
Requires git installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 81,352 stars on the source repository.
What this skill does
Version Release Workflow This skill is a router. The detailed steps live in references/. Scope Boundary (Important) This skill is only for: 1. Release branch / PR workflow 2. CI trigger constraints (auto-tag-release.yml) 3. GitHub Release note writing This skill is not for writing docs/changelog/.mdx.\ If the user asks for website changelog pages, load ../docs-changelog/SKILL.md. Mandatory Companion Skill For every /version-release execution, you MUST load and apply: ../../../DESIGN.md (Voice & Content) Overview The primary development branch is canary. All day-to-day development happens on canary. When releasing, canary is merged into main. Conventional release PRs (🚀 release: …, release/, hotfix/) get a package.json bump commit from release-pr-version.yml while the PR is open. After merge, auto-tag-release.yml tags the merge commit and creates the GitHub Release. sync-main-to-canary runs on push to main. Only two release types are used in practice (major releases are extremely rare and can be ignored): Type Use Case Frequency Source Branch PR Title Format Version Reference ----- ---------------------------------------------- --------------------- -------------- ------------------------------------ ------------- --------------------------------------- Minor Feature iteration release \~Every 4 weeks canary 🚀 release: v{x.y.0} Manually set references/minor-release.md Patch Weekly release / hotfix / model / DB migration \~Weekly or as needed canary or main Custom (e.g. 🚀 release: 20260222) Auto patch +1 references/patch-release-scenarios.md For writing the release-note body (any release type), see references/release-notes-style.md. Auto-Release Trigger Rules (auto-tag-release.yml) After a PR is merged into main, CI determines whether to release based on the following priority: 1. Minor Release (Exact Version) PR title matches 🚀 release: v{x.y.z} -> uses the version number from the title. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills lobehub/version-release--59288e