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

Release

by cdpuk in cdpuk/ha-bestway

Cut a release of this integration - bump the version in manifest.json, run the validation gates, commit, tag the merged commit, and draft categorised release notes for the GitHub release form.

MITAuto-check passedDevelopment

Install Release

skills CLI
$ npx skills add cdpuk/ha-bestway --skill release -a claude-code

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

GitHub CLI
$ gh skill install cdpuk/ha-bestway 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/cdpuk/ha-bestway.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release .claude/skills/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
release
GitHub stars
134
Token cost
~998 tokens
SKILL.md length
482 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Cut a release of this integration - bump the version in manifest.json, run the validation gates, commit, tag the merged commit, and draft categorised release notes for the GitHub release form.

  • Prepare a release
  • SKILL.md covers Never, Work out which stage you are in, Stage A - bump and Stage B - tag and draft notes
  • Calls git, gh and uv
  • Bump the version

What it does

Release is an agent skill from cdpuk/ha-bestway. Cut a release of this integration - bump the version in manifest.json, run the validation gates, commit, tag the merged commit, and draft categorised release notes for the GitHub release form. Use when asked to cut or prepare a release, bump the version, prepare X.Y.Z, or tag a release.

Its SKILL.md is about 1000 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, covering Changelog and release notes. It works with GitHub and Home Assistant. The repository describes itself as: Home Assistant integration for Bestway / Lay-Z-Spa hot tubs. The licence is MIT.

When your agent uses it

  • Prepare a release
  • Bump the version

Example prompts

  • “/release”

Requirements

  • Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit f6c66a8. 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
    • uv
    • jq

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

  • Network

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

Release loads about 998 tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 482 words of instructions outside code blocks.

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

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 cdpuk/ha-bestway at commit f6c66a8, republished under its MIT licence (© cdpuk). 482 words, ~998 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).
name
release
description
Cut a release of this integration - bump the version in manifest.json, run the validation gates, commit, tag the merged commit, and draft categorised release notes for the GitHub release form. Use when asked to cut or prepare a release, bump the version, prepare X.Y.Z, or tag a release.

Release

Publishing the GitHub release stays manual. This skill takes it as far as a pushed tag plus a notes draft, then hands over.

custom_components/bestway/manifest.json is the only file carrying the release version. Do not touch the others: pyproject.toml's 0.1.0 is an unpublished placeholder, hacs.json's homeassistant key is a support floor that moves on its own schedule, and the README badge reads from the GitHub releases API.

Tags are vX.Y.Z, lightweight (git tag, never git tag -a).

Never

  • Publish the release. No gh release create, no gh release edit.
  • Push a tag without asking first. Once HACS sees a tag it is out.
  • Force-push, or delete or move an existing tag.
  • Merge the bump PR yourself.

Work out which stage you are in

Take the target version from the argument, or propose the next patch above the newest tag if none was given. Then:

bash
git fetch origin --tags --quiet
git tag --list 'v*' --sort=-v:refname | head -1
git show origin/main:custom_components/bestway/manifest.json | jq -r .version
  • origin/main does not yet have the target version → stage A.
  • origin/main has it and tag vX.Y.Z does not exist → stage B.
  • The tag already exists → stop. Say so, and offer only the notes draft.

Stage A - bump

Preflight. On any failure, stop and explain which check failed and why:

  • The working tree is clean, or its only change is the manifest version already edited to the target. Adopt that edit rather than rewriting it.
  • The target matches ^[0-9]+\.[0-9]+\.[0-9]+$. Strip a leading v if the user typed one; reject anything else, including a stray dot.
  • The target sorts strictly above the newest existing tag.
  • Neither refs/tags/vX.Y.Z nor origin's copy of it exists.

Report version drift when the committed manifest version does not match the newest tag. It means earlier releases shipped the wrong version to HACS. Say what the gap is; the bump then closes it going forward.

Then bump and validate:

bash
uv run pytest -qq --timeout=10 --durations=10 -n auto \
  --cov custom_components.bestway -o console_output_style=count \
  -p no:sugar tests
uv run pre-commit run --all-files

Commit, matching whichever convention the branch implies - Version X.Y.Z on main, Prepare for X.Y.Z on a prepare-X.Y.Z branch. If anything else rides along (a pre-commit autoupdate, a Python retarget), list it in the commit body.

Push the branch. If it is not main, print the PR link and stop there: the tag has to land on the commit that reaches main.

Show full SKILL.md (126 more words)Show less

Stage B - tag and draft notes

Re-check that origin/main's manifest version equals the target before anything else, then tag that commit and ask before pushing:

bash
git tag "v$VERSION" origin/main
git push origin "v$VERSION"

Draft the notes from GitHub's own generator, which produces the same "What's Changed" body used by past releases:

bash
gh api repos/cdpuk/ha-bestway/releases/generate-notes \
  -f tag_name="v$VERSION" -f previous_tag_name="$PREVIOUS_TAG" \
  --jq .body

Regroup those lines under Features:, Fixes:, Docs: and Chores:. PRs here carry no labels and no commit-message prefixes, so the grouping is a judgement call from the titles. Copy each * <title> by @<author> in <url> line through verbatim, and leave any ## New Contributors block and the **Full Changelog**: line exactly as generated. Drop nothing: every generated line lands in some group.

Write the draft to the scratchpad, print it, and hand over the release form:

https://github.com/cdpuk/ha-bestway/releases/new?tag=vX.Y.Z

The release name is the tag string verbatim.

© cdpuk, MIT. 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/release of cdpuk/ha-bestway.

Open the folder on GitHubat commit f6c66a8

Compare with similar skills

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.

Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release this skillcdpuk/ha-bestway134—~998Automated safety check: PassMIT
Releasekellerza/sunsynk339—~920Automated safety check: PassApache-2.0
GitHub Issue Solverhomeassistant-extras/device-card129—~3.4kAutomated safety check: PassMIT
Releasedcb/homeassistant-claude-kit123—~3.1kAutomated safety check: PassMIT
Beta Prereleaservdbreemen/OTGW-firmware207—~2.7kAutomated safety check: PassGPL-3.0
Cutting A ReleaseTriliumNext/Trilium38k—~3.2kAutomated safety check: PassAGPL-3.0

Similar skills

  • Release

    kellerza/sunsynk

    Bump sunsynk version (major/minor/bugfix), rewrite the Unreleased changelog heading, commit, push to main, and open a draft GitHub release with a v-prefixed tag.

    339 GitHub stars~920 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • GitHub Issue Solver

    homeassistant-extras/device-card

    Accept a GitHub issue URL or issue details, create a comprehensive plan (in plan mode - shows plan first), then implement the solution including tests and documentation, create/update release notes…

    129 GitHub stars~3.4k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Release

    dcb/homeassistant-claude-kit

    Cut a new homeassistant-claude-kit version. An agent skill from dcb/homeassistant-claude-kit.

    123 GitHub stars~3.1k tokensUpdated 5 days ago
    DevelopmentAuto-check passed

  • Beta Prerelease

    rvdbreemen/OTGW-firmware

    Publish an OTGW-firmware beta prerelease — bump VERSIONPRERELEASE, push to otgw-1.x.x, tag, and let CI build + publish the GitHub prerelease

    207 GitHub stars~2.7k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Cutting A Release

    TriliumNext/Trilium

    A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.

    38k GitHub stars~3.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Mole CLI Release Flow

    tw93/Mole

    Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.

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

Works with

Categories

Questions about Release

What does Release do?

Cut a release of this integration - bump the version in manifest.json, run the validation gates, commit, tag the merged commit, and draft categorised release notes for the GitHub release form. Release is an agent skill from cdpuk/ha-bestway.json, run the validation gates, commit, tag the merged commit, and draft categorised release notes for the GitHub release form.

When should I use Release?

Release fits situations like: prepare a release; bump the version.

How do I install Release in Claude Code?

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

How do I install Release in Codex?

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

Can I use 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 cdpuk/ha-bestway --skill 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/release, .gemini/skills/release, .github/skills/release and .opencode/skills/release in your project.

What does Release need to run?

Going by SKILL.md and its folder, Release needs the command-line tools its instructions call (git, gh, uv and jq). Our summary lists: Python 3.

Does Release access the network?

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

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

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

How many tokens does Release use?

About 998 tokens (SKILL.md is roughly 4k 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 Release?

Skills that share tags, products or a category with Release: Release (kellerza/sunsynk, 339 stars), GitHub Issue Solver (homeassistant-extras/device-card, 129 stars), Release (dcb/homeassistant-claude-kit, 123 stars) and Beta Prerelease (rvdbreemen/OTGW-firmware, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

cdpuk (a GitHub user) maintains it in cdpuk/ha-bestway, which has 134 GitHub stars. The repository was last updated on September 6, 2026.

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