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
Release Workflow
Use this skill when preparing a HACS release for the SEMS integration.
Steps
- Update the semantic version in custom_components/sems/manifest.json.
- For beta releases from branches, use the
x.x.x-betaversion format and mark the GitHub Release as a Pre-release. - Create a git tag for the new version:
x.x.x(-beta). - Publish a GitHub Release for that tag. Tags alone are not enough for HACS; the latest release tag is what remote version checks use.
- Write release notes that summarize the changes since the previous release, ideally based on commits since the prior tag.
Validation
- Run the narrowest relevant tests before releasing.
- Run
ruff checkandruff format --checkfor the touched area if code changed. - Confirm the manifest version matches the tag and release metadata.
Notes
- Keep release notes concise and focused on user-visible changes.
- For pre-releases, make the beta/pre-release state explicit in both the version and the GitHub Release settings.
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 | 2mo | No flags | Intermediate |
| agent-workflow-automation | 4 | 6mo | Review | Advanced |
| project-os | 1 | 6mo | Review | Intermediate |
| project-tooling | 1 | 4mo | 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'