version-release
Version release workflow — release process and GitHub Release notes (not docs/changelog pages).
Profile →npx skills add lobehub/lobehub --skill version-release --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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. After merge, `auto-tag-release.yml` automatically handles tagging, version bumping, creating a GitHub Release, and syncing back to the canary branch. 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 | | ----- | ---------------------------------------------- | --------------------- | -------------- | ------------------------------------ | ------------- | -----------------------
- Scope Boundary (Important)
- Mandatory Companion Skill
- Overview
- Auto-Release Trigger Rules (auto-tag-release.yml)
- 1. Minor Release (Exact Version)
- 2. Patch Release (Auto patch +1)
- 3. No Trigger
- Post-Release Automated Actions
- Agent Action Guide
- Precheck (applies to all release types)
- Routing
- Hard Rules (apply to every release type)
What does the version-release skill do?
Version release workflow — release process and GitHub Release notes (not docs/changelog pages).
How do I install it?
Run `npx skills add lobehub/lobehub --skill version-release --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From lobehub/lobehub, a repository with 81,252 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.