Agent skill · software engineering · dohooo
helmor-release
Prepare Helmor releases by inspecting the current branch, drafting a concise user-facing Changesets entry first (bump + body — keep it as short as possible), creating any needed pending in-app release announcement under `.announcements/`, and then showing the user the result with a short menu of adjustments they can pick from. Use when the user wants to cut a release, write a changeset, decide patch/minor/major, draft GitHub release notes, create a release announcement, or summarize branch changes into release-ready language.
Why this skill is useful
Adds an executable script for automating the release process and generating changesets and announcements, which the AI cannot generate on its own.
What it needs
Requires python installed locally. About 6k tokens when loaded. Last updated 2026-08-07. 1,281 stars on the source repository.
What this skill does
Helmor Release Use this skill to turn a branch's real changes into release metadata for Helmor: a clean .changeset/.md entry a pending .announcements/.json fragment when the change deserves an in-app "New in vX" toast Workflow 1. Inspect the branch before asking the user anything. 2. Run scripts/collectreleasecontext.py to gather: commits since the base branch changed files grouped by area a short suggested summary 3. Draft the full changeset yourself, without asking the user upfront. Decide: the bump (patch / minor / major) using the Versioning Guidance below the body shape — one prose sentence when one sentence is genuinely enough, or summary line + bullets when there are multiple distinct user-visible changes (see Default Changeset Format) the actual prose / bullets Prefer a conservative bump (patch unless there is a clear new user-visible capability). If you genuinely cannot decide the bump from the diff alone, default to patch and flag it in the confirmation step. Brevity bias. Aim for the shortest sentence that names the user-visible change — if a clause can be dropped without losing meaning, drop it. Reserve summary+bullets for releases with ≥2 distinct user-visible items. 4. Write the changeset to a single file under .changeset/ right away. Do not wait for approval before creating the file — the user will adjust from a real draft, not a hypothetical one. 5. Decide whether an in-app release announcement is warranted. Create one pending file under .announcements/ only for new user-visible features or workflow changes. Skip bug fixes, internal refactors, routine performance work, and release plumbing unless users need to learn a new behavior. Do not write an id or version. bun run release:version consumes all pending announcement files and merges them into one catalog entry for the final version. 6. Then, and only then, show the user what you created and offer the adjustment menu described in "Confirmation Style". …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills dohooo/helmor-release