Automates HACS integration release workflows.
Install
mkdir -p .claude/skills/release-timsoethout && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15851" && unzip -o skill.zip -d .claude/skills/release-timsoethout && rm skill.zipInstalls to .claude/skills/release-timsoethout
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when managing HACS releases for this integration, including version bumps, tags, beta/pre-release publishing, and release notes.Key capabilities
- →Update the semantic version in manifest.json
- →Use `x.x.x-beta` format for beta releases
- →Create a git tag for the new version
- →Publish a GitHub Release for that tag
- →Write release notes summarizing changes
How it works
This skill manages HACS releases by updating the semantic version in the manifest, creating git tags, publishing GitHub Releases, and compiling release notes. It ensures proper versioning and communication for the integration.
Inputs & outputs
When to use release
- →Bump version for release
- →Create release tag
- →Write release notes
About this skill
HACS Release
- Version: Update
custom_components/sems/manifest.json. Base the next stable version on the latest stable release: patch for fixes, minor for features, major for breaking changes. Use numbered prereleases (for example,11.12.0-beta.1) for the intended stable version; breaking beta changes target the next major. Never reuse a published tag. - Release notes: Update RELEASE_NOTES.md with all user-visible changes since the previous stable tag, including every beta. Keep notes concise; preserve existing links, add verified links when available, and never invent them. Include limitations and compatibility notes.
- Contributors: Credit code authors and people who contributed information, testing, or troubleshooting. Verify GitHub handles; do not infer them from email addresses.
- Publish: Tag with the manifest version and publish a GitHub Release. Mark betas as prereleases; stable releases are regular releases. Copy the release notes into the release description. Publishing triggers
.github/workflows/release.ymlto upload the ZIP; a tag alone is insufficient.
For a stable release after betas, use the same version number and preserve the full beta history in its notes. HACS users must opt into prereleases to receive betas.
Before finishing
- Run the narrowest relevant tests; if code changed, run
ruff checkandruff format --checkon the touched area. - Confirm manifest/tag versions match, prerelease status is correct, and the ZIP uploaded.
When not to use it
- →The task is not related to HACS releases
- →The task is about internal versioning not exposed to HACS
Limitations
- →The skill is for managing HACS releases for this integration
- →Tags alone are not enough for HACS; the latest release tag is what remote version checks use
- →For pre-releases, make the beta/pre-release state explicit in both the version and the GitHub Release settings
How it compares
This workflow automates the specific steps required for HACS releases, including version formatting and GitHub Release creation, providing a structured process compared to manual release management.
Compared to similar skills
release side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| release (this skill) | 0 | 4mo | No flags | Intermediate |
| agent-workflow-automation | 4 | 7mo | Review | Advanced |
| project-os | 1 | 8mo | Review | Intermediate |
| project-tooling | 1 | 5mo | Caution | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
agent-workflow-automation
ruvnet
Agent skill for workflow-automation - invoke with $agent-workflow-automation
project-os
Peiiii
AI project OS for autonomous loop, automated orchestration, and rule-driven execution.
project-tooling
alinaqi
gh, vercel, supabase, render CLI and deployment platform setup
release-version
corvo007
Use when releasing a new version - guides through version bump, changelog generation, commit grouping, tagging, and GitHub CI tracking. Triggers on "发布新版本", "release", "发版", or version release requests.
Release
tobagin
Create a new Keymaker release — analyze changes, bump version, update changelog/README/AppStream metadata, build, commit, tag, push, and create GitHub release
release
RajwanYair
Bump the version, update the changelog, tag, and publish a GitHub release for RegiLattice. Use when preparing a new release, updating version numbers, creating a CHANGELOG entry, or pushing a version tag to trigger the CI release workflow. Triggers on: 'bump version', 'release', 'publish', 'version'