helmor-release

# 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/collect_release_context.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 re...