Release
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.
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.
Install Release
$ npx skills add kellerza/sunsynk --skill release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install kellerza/sunsynk release --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/kellerza/sunsynk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/release .claude/skills/release && rm -rf skills-srcUse ~/.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/
Install the "release" agent skill from https://github.com/kellerza/sunsynk/tree/main/.cursor/skills/release into .claude/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/kellerza/sunsynk/tree/main/.cursor/skills/releaseType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add kellerza/sunsynk --skill release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install kellerza/sunsynk release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kellerza/sunsynk.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/release .agents/skills/release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release" agent skill from https://github.com/kellerza/sunsynk/tree/main/.cursor/skills/release into .agents/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kellerza/sunsynk --skill release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install kellerza/sunsynk release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kellerza/sunsynk.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/release .cursor/skills/release && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "release" agent skill from https://github.com/kellerza/sunsynk/tree/main/.cursor/skills/release into .cursor/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/kellerza/sunsynk.git --path .cursor/skills/release--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add kellerza/sunsynk --skill release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install kellerza/sunsynk release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kellerza/sunsynk.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/release .gemini/skills/release && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "release" agent skill from https://github.com/kellerza/sunsynk/tree/main/.cursor/skills/release into .gemini/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install kellerza/sunsynk releaseInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add kellerza/sunsynk --skill release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/kellerza/sunsynk.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/release .github/skills/release && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "release" agent skill from https://github.com/kellerza/sunsynk/tree/main/.cursor/skills/release into .github/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add kellerza/sunsynk --skill release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install kellerza/sunsynk release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/kellerza/sunsynk.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/release .opencode/skills/release && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "release" agent skill from https://github.com/kellerza/sunsynk/tree/main/.cursor/skills/release into .opencode/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
release- GitHub stars
- 339
- Token cost
- ~920 tokens
- SKILL.md length
- 432 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
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.
- Works in 3 steps: Current branch is main → Working tree is clean (git status… → Bump parameter is one of major | minor |…
- The user asks to release
- SKILL.md covers Parameter, Preconditions (abort if unmet), Steps and Implementation notes, plus 1 more section
- Calls git and gh
What it does
Release is an agent skill from 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. Use when the user asks to release, bump version, or cut a major/minor/bugfix release.
Its SKILL.md is about 920 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: Deye/Sunsynk Inverter Python library and Home Assistant OS Addon. The licence is Apache-2.0.
When your agent uses it
- The user asks to release
- Cut a major/minor/bugfix release
Example prompts
- “/release”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Current branch is main
- Working tree is clean (git status --porcelain empty)
- Bump parameter is one of major | minor | bugfix
What it can do on your machine
Read from SKILL.md and the folder at commit 4628ca7. 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:
gitgh
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
Release loads about 920 tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 432 words of instructions outside code blocks.
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 kellerza/sunsynk at commit 4628ca7, republished under its Apache-2.0 licence (© kellerza). 432 words, ~920 tokens.
Download SKILL.mdSave it as
.claude/skills/release/SKILL.md (or your agent's skills folder).- name
- release
- description
- 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. Use when the user asks to release, bump version, or cut a major/minor/bugfix release.
- disable-model-invocation
- true
Release
Bump version, push to main, and open a draft GitHub release (v0.0.0 tag). Publishing the
draft (not creating it) starts CI.
Parameter
Require one bump kind (ask if missing):
| Input | Semver effect |
|---|---|
major | X.Y.Z → (X+1).0.0 |
minor | X.Y.Z → X.(Y+1).0 |
bugfix | X.Y.Z → X.Y.(Z+1) |
Preconditions (abort if unmet)
Run from the sunsynk repo root. Stop with a clear message unless all pass:
- Current branch is
main - Working tree is clean (
git status --porcelainempty) - Bump parameter is one of
major|minor|bugfix
Steps
- Rebase against the current head:
git pull --rebase - Bump the version in
pyproject.tomlaccording to the input - Use the new version string and change the
## Unreleasedheading inhass-addon-sunsynk-edge/CHANGELOG.mdto## Release x.x.x - Copy
hass-addon-sunsynk-edge/CHANGELOG.mdtohass-addon-sunsynk-multi/CHANGELOG.md - In
www/docs/reference/multi-options.md, remove every edge-only option prefix<i-mdi-dev-to class="vp-edge-option-icon" />(list items and table cells). Leave the::: tipblock unchanged — it stays for future edge-only options. - Commit using the release number (
0.0.0form) as the message and push to GitHub - Create a draft GitHub release with tag
v0.0.0(semantic version preceded byv) - Notify the user to review and publish the draft release on GitHub to start the release process
Implementation notes
Read current version from
[project]→version = "..."inpyproject.toml.Heading match is case-insensitive for
## Unreleased; write## Release <new_version>(novprefix).Stage only
pyproject.toml,hass-addon-sunsynk-edge/CHANGELOG.md,hass-addon-sunsynk-multi/CHANGELOG.md, andwww/docs/reference/multi-options.md(if the edge prefixes were present). Includeuv.lockif the version bump changed it. The multi CHANGELOG copy is the one allowed hand-edit underhass-addon-sunsynk-multi/in this skill (overwrite; do not merge).When stripping edge prefixes, delete the HTML tag and the space after it so bullets stay
- \OPTION`` (or the table cell starts with the backtick). Do not touch the tip, and do not rewrite surrounding option text.Do not copy
config.yamlhere. On a published release,deployer2.ymlcopies edgeconfig.yaml,translations/, andapparmor.txtonto stable exceptname/slug, then setsversionto the tag.Commit message is exactly the new version string (e.g.
0.9.4), nothing else.Push:
git pushtooriginonmain(this skill authorizes push).Draft release (after push), with network/
ghpermissions as needed:bash gh release create "v${VER}" --draft --generate-notes --target main --title "v${VER}"Tag must be
v+ version (e.g.v0.9.4). CI strips the leadingvwhen checking againstpyproject.toml. Do not use--lateston a draft.Do not publish the release; leave it draft so the user can review notes first.
release.publishedis what starts CI.
Show full SKILL.md (36 more words)Show less
Done message
Tell the user the new version, that the commit was pushed, link the draft release URL from gh, and
that they should publish the draft on GitHub when ready to start CI (PyPI + add-ons).
© kellerza, Apache-2.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 .cursor/skills/release of kellerza/sunsynk.
Open the folder on GitHubat commit 4628ca7
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Release this skillkellerza/sunsynk | 339 | — | ~920 | Automated safety check: Pass | Apache-2.0 | |
| Releasecdpuk/ha-bestway | 134 | — | ~998 | Automated safety check: Pass | MIT | |
| GitHub Issue Solverhomeassistant-extras/device-card | 129 | — | ~3.4k | Automated safety check: Pass | MIT | |
| Releasedcb/homeassistant-claude-kit | 123 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Beta Prereleaservdbreemen/OTGW-firmware | 207 | — | ~2.7k | Automated safety check: Pass | GPL-3.0 | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 |
Similar skills
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…
Release
dcb/homeassistant-claude-kit
Cut a new homeassistant-claude-kit version. An agent skill from dcb/homeassistant-claude-kit.
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
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.
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.
Related
Works with
Categories
Questions about Release
What does Release do?
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. Release is an agent skill from 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.
When should I use Release?
Release fits situations like: the user asks to release; cut a major/minor/bugfix release.
How do I install Release in Claude Code?
Run `npx skills add kellerza/sunsynk --skill release -a claude-code`. Or copy the skill folder (.cursor/skills/release in kellerza/sunsynk) 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 kellerza/sunsynk --skill release -a codex`. Or copy the skill folder (.cursor/skills/release in kellerza/sunsynk) 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 kellerza/sunsynk --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 and gh).
Does 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 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 Apache-2.0 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 920 tokens (SKILL.md is roughly 3.7k 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 (cdpuk/ha-bestway, 134 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?
kellerza (a GitHub user) maintains it in kellerza/sunsynk, which has 339 GitHub stars. The repository was last updated on October 6, 2026.
Source: kellerza/sunsynk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.