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

Create Release

by lablup in lablup/backend.ai-webui

Create a release branch, tag, and GitHub release for Backend.AI WebUI.

LGPL-3.0Auto-check passedDevelopment

Install Create Release

skills CLI
$ npx skills add lablup/backend.ai-webui --skill create-release -a claude-code

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

GitHub CLI
$ gh skill install lablup/backend.ai-webui create-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/lablup/backend.ai-webui.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/create-release .claude/skills/create-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
create-release
GitHub stars
133
Token cost
~1.5k tokens
SKILL.md length
539 words
Files
1
Skills in repo
13
Repo updated
First seen
Licence
LGPL-3.0

At a glance

Create a release branch, tag, and GitHub release for Backend.AI WebUI.

  • Works in 9 steps: Validate Prerequisites → Create Release Branch → Update Version in package.json → …
  • Development work in your project
  • SKILL.md covers Arguments, Process, Output Summary and Example, plus 1 more section
  • Calls git, gh and make

What it does

Create Release is an agent skill from lablup/backend.ai-webui. Create a release branch, tag, and GitHub release for Backend.AI WebUI.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with GitHub, npm and React. The repository describes itself as: Backend.AI Web UI for web / desktop app (Windows/Linux/macOS). Backend.AI Web UI provides a convenient environment for users, while allowing various commands to be executed… The licence is LGPL-3.0.

When your agent uses it

  • Development work in your project

Example prompts

  • “/create-release”

Workflow steps

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

  1. Validate Prerequisites
  2. Create Release Branch
  3. Update Version in package.json
  4. Run make versiontag
  5. Commit All Changes
  6. Create Version Tag
  7. Push Branch and Tag to Remote
  8. Create GitHub Release
  9. Improve Release Notes

What it can do on your machine

Read from SKILL.md and the folder at commit 10554dc. 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
    • gh
    • make

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

  • Network

    No URLs in SKILL.md. Its commands use git and gh, 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

Create Release loads about 1.5k tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 539 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~21
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

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

The full file from lablup/backend.ai-webui at commit 10554dc, republished under its LGPL-3.0 licence (© lablup). 539 words, ~1,545 tokens.

Download SKILL.mdSave it as .claude/skills/create-release/SKILL.md (or your agent's skills folder).
name
create-release
description
Create a release branch, tag, and GitHub release for Backend.AI WebUI.
argument-hint
[26.4.0 | 26.4.0-alpha.1 | 26.4.0-beta.0]
model
sonnet
disable-model-invocation
true

Create Release

Create a release branch, tag, and GitHub release for Backend.AI WebUI.

Arguments

$ARGUMENTS specifies the version to release (e.g., 26.4.0, 26.4.0-alpha.1, 26.4.0-beta.0).

If Arguments Not Provided

Automatically determine the next version:

  1. Read current version from root package.json
  2. Parse the version: extract MAJOR.MINOR.PATCH and any prerelease suffix
  3. Present options via AskUserQuestion:
AskUserQuestion({
  questions: [{
    question: "Which version do you want to release?",
    header: "Release Version",
    multiSelect: false,
    options: [
      { label: "MAJOR.MINOR.PATCH (Stable Release)", description: "Release as stable version" },
      { label: "MAJOR.MINOR.PATCH-alpha.N (Alpha)", description: "Alpha pre-release for testing" },
      { label: "MAJOR.MINOR.PATCH-beta.N (Beta)", description: "Beta pre-release for wider testing" },
      { label: "MAJOR.MINOR.PATCH-rc.N (Release Candidate)", description: "Release candidate before stable" },
      { label: "Custom version", description: "Enter a custom version string" }
    ]
  }]
})

Adjust the option labels with actual computed versions based on the current version:

  • If current is 26.4.0-alpha.0: suggest 26.4.0-alpha.1, 26.4.0-beta.0, 26.4.0-rc.0, 26.4.0
  • If current is 26.4.0: suggest 26.4.1, 26.5.0-alpha.0, 26.5.0, 27.0.0-alpha.0
  • Increment the prerelease number if same type already exists

If user selects "Custom version", ask them to type it.

Process

1. Validate Prerequisites
  • Ensure current branch is main and working directory is clean (git status)
  • If not clean, warn the user and stop
  • Validate version format: X.Y.Z or X.Y.Z-{alpha|beta|rc}.N
2. Create Release Branch

Create a branch named MAJOR.MINOR (e.g., 26.4) from main:

bash
git checkout -b 26.4

If the branch already exists, check it out and merge the latest main into it:

bash
git fetch origin main
git checkout 26.4
git merge origin/main -m "chore: merge main into 26.4 for v{VERSION} release"

Merge origin/main, not the local main — a stale local branch would cut the release short.

If the merge has conflicts, warn the user and stop — do not force-resolve conflicts automatically.

3. Update Version in package.json

Use the Edit tool to set the version field in root /package.json to the target version (e.g., 26.4.0 or 26.4.0-alpha.1).

4. Run make versiontag

This propagates the version to all related files:

  • version.json
  • index.html
  • manifest.json
  • react/package.json
  • packages/backend.ai-ui/package.json
  • electron-app/package.json
bash
make versiontag
5. Commit All Changes

Stage all modified files and commit:

bash
git add -A
git commit -m "release: v{VERSION}"
6. Create Version Tag
bash
git tag v{VERSION}
7. Push Branch and Tag to Remote
bash
git push -u origin {MAJOR.MINOR}
git push origin v{VERSION}
8. Create GitHub Release

Determine the base tag for auto-generated release notes:

Show full SKILL.md (286 more words)Show less
Base Tag Selection Logic

  1. List all tags sorted by version:

    bash
    git tag --sort=-version:refname

  2. Determine the base tag:

    • If releasing a stable version (e.g., v26.4.0):
      • Find the most recent stable release tag (no -alpha, -beta, -rc suffix)
      • Skip the tag we just created
    • If releasing a prerelease version (e.g., v26.4.0-alpha.1):
      • Find the most recent tag of ANY type (stable or prerelease)
      • Skip the tag we just created
      • Pick the latest one as the base

  3. Create the release:

    bash
    gh release create v{VERSION} \
  --title "v{VERSION}" \
  --generate-notes \
  --notes-start-tag {BASE_TAG} \
  --target {BRANCH}

    For prerelease versions (alpha/beta/rc), add --prerelease flag.

  4. Immediately report the release link. As soon as the gh release create command returns the release URL, surface it to the user right away in a short, standalone message (e.g. ✅ Release created: <url>) — do not wait until the final Output Summary. Then proceed to the next step without pausing for confirmation.

9. Improve Release Notes

After the GitHub release is created, invoke the /fw:release-note skill to improve and format the release notes:

/fw:release-note v{VERSION}

This will:

  • Fetch the auto-generated release notes
  • Categorize and group changes with emojis
  • Add contextual descriptions
  • Ask for user confirmation before updating

Output Summary

After completion, provide:

  1. Release Branch: branch name that was created/used
  2. Version: the released version
  3. Tag: the git tag created
  4. Base Tag: the tag used as comparison base for release notes
  5. GitHub Release URL: link to the created release

Example

User: /create-release 26.4.0

1. Validates main branch is clean
2. Creates branch 26.4
3. Updates package.json to 26.4.0
4. Runs make versiontag
5. Commits: "release: v26.4.0"
6. Tags: v26.4.0
7. Pushes branch 26.4 and tag v26.4.0
8. Creates GitHub release (base: v26.3.0)
9. Runs /fw:release-note v26.4.0 to improve notes

User: /create-release 26.4.0-beta.0

1. Validates main branch is clean
2. Branch 26.4 already exists → checks it out and merges main into 26.4
3. Updates package.json to 26.4.0-beta.0
4. Runs make versiontag
5. Commits: "release: v26.4.0-beta.0"
6. Tags: v26.4.0-beta.0
7. Pushes branch 26.4 and tag v26.4.0-beta.0
8. Creates GitHub pre-release (base: v26.4.0-alpha.1)
9. Runs /fw:release-note v26.4.0-beta.0 to improve notes

Notes

  • This skill uses git directly for branch/tag operations (not gh stack) because release branches follow a different workflow than feature PRs
  • Stable versions are published releases; alpha/beta/rc versions are marked as pre-releases
  • Always confirm with the user before pushing to remote if anything looks unexpected

© lablup, LGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/create-release of lablup/backend.ai-webui.

Open the folder on GitHubat commit 10554dc

Compare with similar skills

Create 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.

Create Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Create Release this skilllablup/backend.ai-webui133—~1.5kAutomated safety check: PassLGPL-3.0
Dependabot Alerts Updatelivesession/xyd114—~2kAutomated safety check: PassMIT
Release WorkflowCaldis/react-zmage946—~3.6kAutomated safety check: NotesMIT
Release New Versionkcsujeet/ilamy-calendar351—~5.8kAutomated safety check: PassMIT
Octane React Library Portoctanejs/octane1.4k—~2.5kAutomated safety check: PassMIT
Linea Dependency MaintenanceConsensys-Incorporated/linea-attestation-registry1771 repos~3.7kAutomated safety check: WarnMIT

Similar skills

  • Dependabot Alerts Update

    livesession/xyd

    Automatically fetch and fix Dependabot security alerts by querying GitHub REST API for open alerts, identifying vulnerable packages, researching secure versions, and updating package.json files…

    114 GitHub stars~2k tokensUpdated 15 days ago
    DevelopmentAuto-check passed

  • Release Workflow

    Caldis/react-zmage

    A skill your agent uses when the user wants to ship a new version of react-zmage to npm.

    946 GitHub stars~3.6k tokensUpdated 4 mo ago
    DevelopmentAuto-check: notes

  • Release New Version

    kcsujeet/ilamy-calendar

    Cut a new release of @ilamy/calendar — analyze commits since the last tag, suggest a semver bump, draft a CHANGELOG entry in the project's existing style, run the CI gate, commit, tag, push to…

    351 GitHub stars~5.8k tokensUpdated 4 days ago
    DevelopmentAuto-check passed

  • Octane React Library Port

    octanejs/octane

    Implement and verify new React-library ports or copied/rewritten React surfaces in Octane bindings from npm names or npm/GitHub links/lists.

    1.4k GitHub stars~2.5k tokensUpdated today
    DevelopmentAuto-check passed

  • Linea Dependency Maintenance

    Consensys-Incorporated/linea-attestation-registry

    Safely plan and execute dependency maintenance for JavaScript/TypeScript (npm, pnpm) and GitHub Actions, including npm lockfiles, pnpm workspaces, catalogs, overrides, SHA-pinned action versions…

    177 GitHub starsUsed in 1 repo~3.7k tokens
    DevelopmentAuto-check: warnings

  • Release Flow

    romankurnovskii/BrewMate

    Automate the full application release flow for BrewMate, including committing local changes, bumping version, waiting for GitHub Actions release build, and pushing the in-repo cask update…

    301 GitHub stars~976 tokensUpdated 10 days ago
    DevOps & CloudAuto-check passed

More from lablup/backend.ai-webui

All 13 skills in this repo

  • Walkthrough

    lablup/backend.ai-webui

    Mint a walkthrough for the PR this session just implemented: a set of numbered stops a reviewer opens in the live dev server, each one marking an element on screen with what changed and what to check.

    133 GitHub stars~4.9k tokensUpdated today
    Auto-check: notes

  • Docs Lead

    lablup/backend.ai-webui

    A skill your agent uses whenever the user mentions docs, the manual, documentation, terminology, translations, or screenshots — including indirect mentions like "이 PR 문서 영향 봐줘", "문서 점검", "용어 통일"…

    133 GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Backend AI Guide

    lablup/backend.ai-webui

    Expert guide for Backend.AI distributed computing platform. An agent skill from lablup/backend.ai-webui.

    133 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed

  • Dev Server

    lablup/backend.ai-webui

    Start the project's development server (pnpm dev for backend.ai-webui; discovered from README/package.json elsewhere), deriving the header color, app name, default backend endpoint and login…

    133 GitHub stars~6.9k tokensUpdated today
    Auto-check: notes

  • Record E2E Gif

    lablup/backend.ai-webui

    Record Playwright e2e tests as one GIF per test case (video → ffmpeg palette GIF) and return a markdown table for a PR description.

    133 GitHub stars~907 tokensUpdated today
    Auto-check: notes

  • Relay Mutation Store Updates

    lablup/backend.ai-webui

    A skill your agent uses when writing if (success) updateFetchKey(), an onRequestClose handler, or any refetch after a mutation; when a setting modal handles both create and update behind one…

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

Works with

Categories

Questions about Create Release

What does Create Release do?

Create a release branch, tag, and GitHub release for Backend.AI WebUI. ai-webui.AI WebUI.

When should I use Create Release?

Create Release fits situations like: development work in your project.

How do I install Create Release in Claude Code?

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

How do I install Create Release in Codex?

Run `npx skills add lablup/backend.ai-webui --skill create-release -a codex`. Or copy the skill folder (.claude/skills/create-release in lablup/backend.ai-webui) into .agents/skills/create-release in your project. Codex loads it when a task matches its description.

Can I use Create 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 lablup/backend.ai-webui --skill create-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/create-release, .gemini/skills/create-release, .github/skills/create-release and .opencode/skills/create-release in your project.

What does Create Release need to run?

Going by SKILL.md and its folder, Create Release needs the command-line tools its instructions call (git, gh and make).

Does Create Release access the network?

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

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

Create Release is published under the LGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Create Release use?

About 1.5k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Create Release?

Skills that share tags, products or a category with Create Release: Dependabot Alerts Update (livesession/xyd, 114 stars), Release Workflow (Caldis/react-zmage, 946 stars), Release New Version (kcsujeet/ilamy-calendar, 351 stars) and Octane React Library Port (octanejs/octane, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create Release?

lablup (a GitHub organization) maintains it in lablup/backend.ai-webui, which has 133 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 7, 2026.

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