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

Installs 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.
132 chars✓ has a “when” trigger
Intermediate

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

You give it
A request to prepare a HACS release for the SEMS integration
You get back
A new HACS release with updated manifest, git tag, GitHub release, and release notes

When to use release

  • →Bump version for release
  • →Create release tag
  • →Write release notes

About this skill

HACS Release

  1. 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.
  2. 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.
  3. Contributors: Credit code authors and people who contributed information, testing, or troubleshooting. Verify GitHub handles; do not infer them from email addresses.
  4. Publish:
    • Stable: Prepare the manifest and stable notes in a PR to master. Merging it triggers .github/workflows/stable-release.yml, which extracts the matching stable notes and creates the GitHub Release. It uses .github/scripts/upload_release_asset.py to attach custom_components/sems/sems.zip. Do not manually tag or publish a stable release. After merge, verify the workflow completed and the ZIP is attached. The workflow skips prerelease versions and avoids re-creating existing releases.
    • Prerelease: Continue to create and publish beta releases manually, mark them as prereleases, and use the matching beta notes. Publishing triggers .github/workflows/release-assets.yml to 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 check and ruff format --check on the touched area.
  • Before merging a stable release-preparation PR, confirm the manifest version matches exactly one stable release-notes section and that the tag is unused; do not publish manually.
  • After merge, confirm the stable GitHub Release tag matches the manifest, it is not a prerelease, and sems.zip is attached.
  • For a manually published prerelease, confirm the tag matches the manifest, the prerelease flag is set, and sems.zip is attached.

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.

SkillInstallsUpdatedSafetyDifficulty
release (this skill)05moNo flagsIntermediate
agent-workflow-automation49moReviewAdvanced
project-os110moReviewIntermediate
project-tooling17moCautionBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry