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.
Create a release or pre-release for hastrava (bumps manifest.json, tags, and publishes a GitHub release with curated notes)
Install Release
$ npx skills add craibo/ha_strava --skill release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install craibo/ha_strava 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/craibo/ha_strava.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/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/craibo/ha_strava/tree/main/.claude/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/craibo/ha_strava/tree/main/.claude/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 craibo/ha_strava --skill release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install craibo/ha_strava release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/craibo/ha_strava.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/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/craibo/ha_strava/tree/main/.claude/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 craibo/ha_strava --skill release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install craibo/ha_strava release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/craibo/ha_strava.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/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/craibo/ha_strava/tree/main/.claude/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/craibo/ha_strava.git --path .claude/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 craibo/ha_strava --skill release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install craibo/ha_strava release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/craibo/ha_strava.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/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/craibo/ha_strava/tree/main/.claude/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 craibo/ha_strava 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 craibo/ha_strava --skill release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/craibo/ha_strava.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/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/craibo/ha_strava/tree/main/.claude/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 craibo/ha_strava --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 craibo/ha_strava release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/craibo/ha_strava.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/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/craibo/ha_strava/tree/main/.claude/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
- 146
- Token cost
- ~1.1k tokens
- SKILL.md length
- 485 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create a release or pre-release for hastrava (bumps manifest.json, tags, and publishes a GitHub release with curated notes)
- Works in 8 steps: Determine current state → Compute the target version → Find the previous reference point → …
- Development work in your project
- SKILL.md covers Versioning rules and Steps
- Calls git and gh
What it does
Release is an agent skill from craibo/ha_strava. Create a release or pre-release for hastrava (bumps manifest.json, tags, and publishes a GitHub release with curated notes)
Its SKILL.md is about 1.1k 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. It works with GitHub and Home Assistant. The repository describes itself as: Strava Activities and Summary data integration for Home Assistant. The licence is MIT.
When your agent uses it
- Development work in your project
Example prompts
- “/release”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 273ffff. 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 1.1k tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 485 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 craibo/ha_strava at commit 273ffff, republished under its MIT licence (© craibo). 485 words, ~1,091 tokens.
Download SKILL.mdSave it as
.claude/skills/release/SKILL.md (or your agent's skills folder).- name
- release
- description
- Create a release or pre-release for ha_strava (bumps manifest.json, tags, and publishes a GitHub release with curated notes)
- disable-model-invocation
- true
Create a release or pre-release for this integration. Ask the user which one they want if it isn't already clear from their request.
Versioning rules
Both releases and pre-releases use plain patch versions (e.g. 4.6.1, 4.6.2) — there is no -beta.N suffix. A pre-release is just a normal version tag published with GitHub's "pre-release" flag instead of "latest"; the version string itself doesn't distinguish the two.
- Target version = the version currently in
custom_components/ha_strava/manifest.json(e.g.4.6.1). - Pre-release: if a tag with that exact version already exists (as either a release or a pre-release), bump the patch number by 1 and use that instead — repeat until the version is unused.
- Release: if a tag with that exact version already exists, STOP and tell the user the manifest needs to be bumped first — do not auto-increment a release version on their behalf.
- Never reuse or go backwards from an existing tag.
Steps
1. Determine current state
cd <repo root>
git status --short # must be clean; if not, stop and tell the user
git fetch --tags
cat custom_components/ha_strava/manifest.json # get the current version
gh release list --limit 10 # see recent releases/pre-releases2. Compute the target version
Start from manifest.json's version field. Check git tag -l "<version>".
- Pre-release: if it already exists, increment the patch number and check again, repeating until you find a version with no existing tag.
- Release: if it already exists, stop and tell the user to bump
manifest.jsonfirst — do not proceed.
Use the resulting version as the target for both the manifest bump and the tag.
3. Find the previous reference point
- Pre-release notes diff against the most recently published tag overall (release or pre-release, whichever is more recent by date) — i.e. the immediately preceding entry in
gh release list. - Release notes diff against the latest published release tag specifically (not a pre-release), covering everything since then (including any pre-releases that led up to it):
gh release list --exclude-pre-releases --limit 1, or filter tags without matching a pre-release marker.
git log <previous-tag>..HEAD --onelineShow full SKILL.md (191 more words)Show less
4. Draft release notes
Compact, clear, bullet points. Group or describe by user-facing change, not by commit.
Exclude commits/changes that are:
- Test-only changes (adding/updating tests, fixing test flakiness)
CLAUDE.md,.claude/, skills, agent configuration, or other AI-tooling meta files- Pure chore/formatting noise with no user-facing effect (unless it's the only content — in which case say so plainly)
Include anything user- or developer-facing: features, fixes, behavior changes, breaking changes, config/docs changes that affect setup.
Format:
## What's Changed
- <concise bullet, semantic-prefix style, no PR/commit spam>
- ...
**Full Changelog**: https://github.com/craibo/ha_strava/compare/<previous-tag>...<target-tag>Keep each bullet to one line where possible. Do not include a testing/test-plan section.
5. Confirm with the user before publishing
Show the user:
- The target version/tag being created
- Whether it's a release or pre-release
- The full drafted release notes
Ask them to confirm or edit before proceeding. Do not tag, push, or create the GitHub release until the user explicitly confirms.
6. Bump manifest and commit
If manifest.json's version doesn't already equal the target version exactly, update it and commit on main — this applies to both releases and pre-releases, since the tag and the manifest always match now:
git commit -m "chore: release <version>"7. Tag and publish
git tag <target-tag>
git push origin <target-tag>Pre-release:
gh release create <target-tag> --title "<target-tag>" --notes "<confirmed notes>" --prereleaseRelease:
gh release create <target-tag> --title "<target-tag>" --notes "<confirmed notes>" --latest8. Share the result
Output the GitHub release URL as a clickable link.
© craibo, 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 craibo/ha_strava.
Open the folder on GitHubat commit 273ffff
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 skillcraibo/ha_strava | 146 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Releasekellerza/sunsynk | 339 | — | ~920 | Automated safety check: Pass | Apache-2.0 | |
| Releasecdpuk/ha-bestway | 134 | — | ~998 | Automated safety check: Pass | MIT | |
| Community Triageroryeckel/wyoming_openai | 218 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| GitHub Issue Solverhomeassistant-extras/device-card | 129 | — | ~3.4k | Automated safety check: Pass | MIT | |
| PR Bodyandrew-blake/melcloudhome | 142 | — | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
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.
Community Triage
roryeckel/wyoming_openai
GitHub issues, pull requests, bug reports, scope questions, and support threads.
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…
PR Body
andrew-blake/melcloudhome
A skill your agent uses when composing or revising a pull request description in this repo, including PRs that sit in a stack.
Acp Issue Diagnose
jrhubott/adaptive-cover-pro
Triage an Adaptive Cover Pro GitHub issue end-to-end — fetch the attached diagnostics file (or take a local path), run a Sonnet-powered diagnosis, and draft a reply ready to post on the issue.
Related
Works with
Categories
Questions about Release
What does Release do?
Create a release or pre-release for hastrava (bumps manifest.json, tags, and publishes a GitHub release with curated notes). Release is an agent skill from craibo/ha_strava.
When should I use Release?
Release fits situations like: development work in your project.
How do I install Release in Claude Code?
Run `npx skills add craibo/ha_strava --skill release -a claude-code`. Or copy the skill folder (.claude/skills/release in craibo/ha_strava) 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 craibo/ha_strava --skill release -a codex`. Or copy the skill folder (.claude/skills/release in craibo/ha_strava) 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 craibo/ha_strava --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 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 1.1k tokens (SKILL.md is roughly 4.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), Release (cdpuk/ha-bestway, 134 stars), Community Triage (roryeckel/wyoming_openai, 218 stars) and GitHub Issue Solver (homeassistant-extras/device-card, 129 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release?
craibo (a GitHub user) maintains it in craibo/ha_strava, which has 146 GitHub stars. The repository was last updated on October 1, 2026.
Source: craibo/ha_strava on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.