Menu
Bump the integration version, create a branch, commit, push, and open a PR.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Based on SOC occupation classification
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/oyvindwe/connectlife-ha --skill bump-versionThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
Fill missing translation keys in the ConnectLife language files using appliance-specific terminology, keep time units in the data dictionary (not baked into entity names), verify, and open one PR per language. Use when a language file is missing keys or when unit words need cleaning out of names.
Generate release notes for a new version by analyzing commits since the last git tag. Groups changes into categorized sections with contributor attribution.
| name | bump-version |
| description | Bump the integration version, create a branch, commit, push, and open a PR. |
| argument-hint | <version> |
| allowed-tools | Read Edit Bash(git *) Bash(gh *) Bash(uv sync) |
Bump the version of this ConnectLife Home Assistant integration.
Determine the new version:
$ARGUMENTS is provided, it must be a valid semver version (e.g., 0.31.0). Use it as the new version.custom_components/connectlife/manifest.json.git log --oneline "$(git log --grep='^Version ' -n 1 --format=%H)..HEAD"
git log --oneline -n 20 if no prior version commit is found.)0.x.y, where per semver the public API is considered unstable — breaking changes do not trigger a 1.0.0 release on their own, they bump MINOR. Reserve a MAJOR bump for a deliberate, user-driven 1.0.0 graduation.
X.0.0): only when the user explicitly asks to graduate to 1.0.0 (or beyond). Do not infer this from commit contents alone while on 0.x.y.0.X.0): new functionality or breaking changes — new device mappings/registrations, new properties, new platforms, new entities, additive API changes, removed/renamed entities or options, incompatible config flow changes, minimum HA version raised.0.0.X): backwards-compatible fixes only — bug fixes, translation-only changes, doc/readme tweaks, internal refactors with no user-visible change.
When in doubt between MINOR and PATCH, pick MINOR.Verify the working tree is clean:
git status --porcelain
If there are uncommitted changes, stop and tell the user.
Make sure main is up to date:
git checkout main
git pull
Create a version branch:
git checkout -b version/<new_version>
Update the version in these files:
custom_components/connectlife/manifest.json — the "version" fieldpyproject.toml — the version fieldRun uv sync to update uv.lock.
Stage and commit:
git add custom_components/connectlife/manifest.json pyproject.toml uv.lock
git commit -m "Version <new_version>"
Push and create PR:
git push -u origin version/<new_version>
gh pr create --title "Version <new_version>" --body "Bump version to <new_version>"
Report the PR URL to the user.