New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

LobeHub Version Release

by lobehub in lobehub/lobehub

Guides the release PR flow, the CI rules that tag a release and the writing of GitHub Release notes for a repo that develops on a canary branch.

Custom licenceAuto-check passedDevelopment

Install LobeHub Version Release

skills CLI
$ npx skills add lobehub/lobehub --skill version-release -a claude-code

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

GitHub CLI
$ gh skill install lobehub/lobehub version-release --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/lobehub/lobehub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/version-release .claude/skills/version-release && 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/

Facts

Skill name
version-release
GitHub stars
83k
Token cost
~1.2k tokens
SKILL.md length
540 words
Files
8 (incl. references)
Skills in repo
50
Repo updated
First seen
Licence
Custom licence

At a glance

Guides the release PR flow, the CI rules that tag a release and the writing of GitHub Release notes for a repo that develops on a canary branch.

  • Works in 3 steps: Minor Release (Exact Version) → Patch Release (Auto patch +1) → No Trigger
  • Preparing a minor release PR from canary into main
  • SKILL.md covers Scope Boundary (Important), Mandatory Companion Skill, Overview and Auto-Release Trigger Rules…, plus 2 more sections
  • Calls git

What it does

Acting as a router for release work in the LobeHub repository, the skill starts from the branch model: day-to-day development happens on canary, and a release means merging canary into main. Release PRs, whether titled with a release prefix or opened from release/* or hotfix/* branches, get a package.json version bump from a workflow while they are open. After the merge, auto-tag-release.yml tags the merge commit and creates the GitHub Release.

Two release types are used in practice. A minor release comes roughly every four weeks with the version set by hand in the PR title, and a patch release comes weekly or as needed, with CI adding one to the patch number. The detailed steps sit in reference files for minor releases, patch scenarios and release-note style, with changelog examples for a database migration, a hotfix and a weekly release. Website changelog pages are out of scope, and the repository's DESIGN.md must be loaded for voice before every run.

When your agent uses it

  • Preparing a minor release PR from canary into main
  • Shipping a weekly patch release or a hotfix
  • Writing the GitHub Release notes for a new version
  • Checking which PR titles or branch names trigger the auto-tag workflow

Example prompts

  • “Prepare this week's patch release PR and draft the GitHub Release notes.”
  • “We need a hotfix release for the broken login. Walk me through the branch and PR title.”
  • “Which PR title formats make auto-tag-release.yml create a release?”

Requirements

  • Access to the LobeHub repository and its release workflows

Workflow steps

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

  1. Minor Release (Exact Version)
  2. Patch Release (Auto patch +1)
  3. No Trigger

What it can do on your machine

Read from SKILL.md and the folder at commit 1863542. 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

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    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

LobeHub Version Release loads about 1.2k tokens when it runs, and up to ~8k if it reads all its reference files. Until then it costs about 28 tokens; SKILL.md has 540 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~28
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~8k

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 540 words (~1,217 tokens).

“This skill is a router. The detailed steps live in references/.”

— opening of SKILL.md by lobehub, Custom licence
name
version-release
disable-model-invocation
true
argument-hint
[minor|patch] [version?]

Read the full SKILL.md on GitHub

Files

SKILL.md and 7 other files (references) in .agents/skills/version-release of lobehub/lobehub.

  • SKILL.md
  • agents/openai.yaml
  • references/changelog-example/db-migration.md
  • references/changelog-example/hotfix.md
  • references/changelog-example/weekly-release.md
  • references/minor-release.md
  • references/patch-release-scenarios.md
  • references/release-notes-style.md

Open the folder on GitHubat commit 1863542

Compare with similar skills

LobeHub Version Release 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.

LobeHub Version Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
LobeHub Version Release this skilllobehub/lobehub83k—~1.2kAutomated safety check: PassCustom licence
EverOS Release WorkflowEverMind-AI/EverOS13k—~1.3kAutomated safety check: PassApache-2.0
Cline CLI Release Publishercline/cline70k—~3.4kAutomated safety check: WarnApache-2.0
ClickUp CLI Release Processkrodak/clickup-cli120—~906Automated safety check: WarnMIT
OpenWork Release Processdifferent-ai/openwork24k—~2.3kAutomated safety check: PassCustom licence
Create GitHub PRopenJiuwen-ai/sciencediscovery148—~3kAutomated safety check: PassApache-2.0

Similar skills

  • EverOS Release Workflow

    EverMind-AI/EverOS

    Walks through cutting a versioned everos release: bump the version, update the changelog, tag it, and review the drafted GitHub Release page before publishing.

    13k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed

  • Cline CLI Release Publisher

    cline/cline

    Walks through releasing the Cline CLI package to npm: release notes, version bump, matching git tag, and either the GitHub workflow or a local publish.

    70k GitHub stars~3.4k tokensUpdated today
    DevelopmentAuto-check: warnings

  • ClickUp CLI Release Process

    krodak/clickup-cli

    Walks through releasing a new version of clickup-cli: pre-release checks, version bump, tagging, CI watch, release notes and the Homebrew update.

    120 GitHub stars~906 tokensUpdated yesterday
    DevOps & CloudAuto-check: warnings

  • OpenWork Release Process

    different-ai/openwork

    Cuts an OpenWork desktop release through a tag-driven GitHub Actions workflow that makes no commits, with pre-tag checks on open fix PRs and verification afterward.

    24k GitHub stars~2.3k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Create GitHub PR

    openJiuwen-ai/sciencediscovery

    Open or update a pull request on GitHub's openJiuwen-ai/sciencediscovery: run the UT/ST/E2E layers locally, push the branch to the operator's own GitHub fork, write a body that says what was…

    148 GitHub stars~3k tokensUpdated 5 days ago
    DevelopmentAuto-check passed

  • GitHub Automation

    davila7/claude-code-templates

    Automate GitHub repositories, issues, pull requests, branches, CI/CD, and permissions via Rube MCP (Composio).

    32k GitHub starsUsed in 5 repos~2.8k tokens
    Productivity & AutomationAuto-check passed

More from lobehub/lobehub

All 50 skills in this repo

  • LobeHub Interactive Prototype

    lobehub/lobehub

    Builds single-file interactive HTML prototypes rendered with the real LobeHub UI components and written as production-style React, so they can later be split into files.

    83k GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Acceptance Evidence for Deliveries

    lobehub/lobehub

    Verifies a delivery end to end by driving the real product on a CLI, web, desktop or iOS Simulator surface, capturing evidence and publishing a round with the lh CLI.

    83k GitHub stars~9.7k tokensUpdated today
    Auto-check passed

  • Git Worktree Cleanup

    lobehub/lobehub

    Audits stale Git worktrees and branches with a bundled script, classifies each one, and deletes only after you approve the exact candidates.

    83k GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • LobeHub Alint Rule Set Maintenance

    lobehub/lobehub

    Maintains LobeHub's model-backed alint rule set: writing rules, removing false positives against real code, deciding warn versus error and tracking token cost.

    83k GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • LobeHub Builtin Tool Authoring

    lobehub/lobehub

    Guides building LobeHub builtin agent tools, from the manifest and execution runtime to executors, chat UI renders and registry wiring.

    83k GitHub stars~2.4k tokensUpdated today
    Auto-check passed

  • LobeHub Data Fetching Layers

    lobehub/lobehub

    Explains how LobeHub client code fetches data through services, SWR store hooks and cache keys, and when to avoid useEffect fetching or duplicated state.

    83k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about LobeHub Version Release

What does LobeHub Version Release do?

Guides the release PR flow, the CI rules that tag a release and the writing of GitHub Release notes for a repo that develops on a canary branch. Acting as a router for release work in the LobeHub repository, the skill starts from the branch model: day-to-day development happens on canary, and a release means merging canary into main.json version bump from a workflow while they are open.

When should I use LobeHub Version Release?

LobeHub Version Release fits situations like: preparing a minor release PR from canary into main; shipping a weekly patch release or a hotfix; writing the GitHub Release notes for a new version; checking which PR titles or branch names trigger the auto-tag workflow.

How do I install LobeHub Version Release in Claude Code?

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

How do I install LobeHub Version Release in Codex?

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

Can I use LobeHub Version Release 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 lobehub/lobehub --skill version-release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/version-release, .gemini/skills/version-release, .github/skills/version-release and .opencode/skills/version-release in your project.

What does LobeHub Version Release need to run?

Going by SKILL.md and its folder, LobeHub Version Release needs the command-line tools its instructions call (git). Our summary lists: Access to the LobeHub repository and its release workflows.

Does LobeHub Version Release access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is LobeHub Version Release 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 LobeHub Version Release use?

LobeHub Version Release has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does LobeHub Version Release use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.8k tokens, read only when the agent opens those files.

What are the alternatives to LobeHub Version Release?

Skills that share tags, products or a category with LobeHub Version Release: EverOS Release Workflow (EverMind-AI/EverOS, 13k stars), Cline CLI Release Publisher (cline/cline, 70k stars), ClickUp CLI Release Process (krodak/clickup-cli, 120 stars) and OpenWork Release Process (different-ai/openwork, 24k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains LobeHub Version Release?

lobehub (a GitHub organization) maintains it in lobehub/lobehub, which has 83,023 GitHub stars. The repository holds 50 skills in this directory. The repository was last updated on October 7, 2026.

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