New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Release Swift

by robinebers in robinebers/openusage

Cut a release of OpenUsage (Swift menu-bar app): pick a version, generate a categorized changelog, tag from main, and publish the GitHub Release with notes.

MITAuto-check passedDevelopment

Install Release Swift

skills CLI
$ npx skills add robinebers/openusage --skill release-swift -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install robinebers/openusage release-swift --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/robinebers/openusage.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release-swift .claude/skills/release-swift && rm -rf skills-src

Use ~/.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/

Facts

Skill name
release-swift
GitHub stars
4.3k
Token cost
~1.6k tokens
SKILL.md length
665 words
Files
1
Skills in repo
25
Repo updated
First seen
Licence
MIT

At a glance

Cut a release of OpenUsage (Swift menu-bar app): pick a version, generate a categorized changelog, tag from main, and publish the GitHub Release with notes.

  • Works in 7 steps: Choose the version → Generate the changelog → Owner approval → …
  • Ship an Early Access beta
  • SKILL.md covers Channels, Cutting a release, Changelog template and Rules
  • Calls gh, git and curl; reaches robinebers.github.io

What it does

Release Swift is an agent skill from robinebers/openusage. Cut a release of OpenUsage (Swift menu-bar app): pick a version, generate a categorized changelog, tag from main, and publish the GitHub Release with notes. Use to ship an Early Access beta or a stable release.

Its SKILL.md is about 1.6k 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, covering iOS development, Changelog and release notes and Feature launches and release readiness. It works with GitHub. The repository describes itself as: Burning through your subscriptions too fast? Paying for stuff you never use? Stop guessing. OpenUsage is free and open source. The licence is MIT.

When your agent uses it

  • Ship an Early Access beta
  • A stable release

Example prompts

  • “/release-swift”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Choose the version
  2. Generate the changelog
  3. Owner approval
  4. Record it in CHANGELOG.md
  5. Tag and push
  6. Publish the notes
  7. Verify (never leave a draft)

What it can do on your machine

Read from SKILL.md and the folder at commit 1c37176. 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:

    • gh
    • git
    • curl

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • robinebers.github.io

    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 Swift loads about 1.6k tokens when it runs. Until then it costs about 57 tokens; SKILL.md has 665 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~57
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

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 robinebers/openusage at commit 1c37176, republished under its MIT licence (© robinebers). 665 words, ~1,640 tokens.

Download SKILL.mdSave it as .claude/skills/release-swift/SKILL.md (or your agent's skills folder).
name
release-swift
description
Cut a release of OpenUsage (Swift menu-bar app): pick a version, generate a categorized changelog, tag from `main`, and publish the GitHub Release with notes. Use to ship an Early Access beta or a stable release.

Release Swift

Pushing a v* tag on main runs .github/workflows/release.yml, which builds, signs, notarizes, attaches OpenUsage-<version>.dmg to the GitHub Release, and updates the Sparkle appcast.xml on gh-pages. CI creates the release with an EMPTY body, so this skill generates the changelog, records it in CHANGELOG.md, and publishes the notes onto the release.

Channels

  • Beta (Early Access): suffixed tag like v0.7.1-beta.1. Marked a GitHub pre-release and added to Sparkle's beta channel. Only users with Early Access enabled get it; GitHub "Latest" is untouched.
  • Stable: plain tag like v0.7.1. Marked non-prerelease, becomes GitHub "Latest", and ships to everyone.

The tag IS the version: v0.7.1-beta.1 becomes CFBundleShortVersionString = 0.7.1-beta.1, and CFBundleVersion is the git commit count. There are no version files to bump.

Cutting a release

1. Choose the version

Next number in the current lane (default bump: patch). Beta builds add a -beta.N suffix. Confirm with the owner before proceeding.

2. Generate the changelog

Collect commits since the previous release in the same channel and categorize each:

  • Stable cut: span from the last stable tag to this one (e.g. v0.7.0...v0.7.1), so the notes roll up the entire beta series plus any post-beta commits. Never start a stable changelog at the last beta — that would omit every beta in the lane.
  • Beta cut: span from the previous tag (the prior beta, or the last stable if it's the first beta in a lane) to this one.
Commit prefixCategory
feat, feature, or starts with "Add"New Features
fix or starts with "Fix"Bug Fixes
refactor, enhanceRefactor
chore, style, docs, perf, test, ci, buildChores
UncategorizedBug Fixes

Author attribution (required on every entry):

  • With a PR number (#123): gh pr view 123 --json author -q '.author.login'.
  • Without a PR number: gh api /repos/robinebers/openusage/commits/{full_hash} -q '.author.login'.
  • If the API returns null, fall back to the git author name.

Output the changelog in a code block (template below) for review.

3. Owner approval

Wait for explicit approval of the changelog before changing any files. Accept edits if offered.

4. Record it in CHANGELOG.md

Prepend the approved section right after the # Changelog header. Commit on main:

sh
git switch main && git pull
git add CHANGELOG.md && git commit -m "docs: changelog for v{version}"
5. Tag and push
sh
git tag -a v{version} -m "v{version}"
git push origin main
git push origin v{version}
6. Publish the notes

CI creates the release with an empty body, so attach the approved notes after it finishes:

sh
gh run watch
gh release view v{version} >/dev/null 2>&1   # confirm CI created the release
gh release edit v{version} --notes-file /tmp/notes-v{version}.md

Never leave a release blank.

Show full SKILL.md (286 more words)Show less
7. Verify (never leave a draft)
sh
gh release view v{version} --json isDraft,isPrerelease,assets,body \
  --jq '{isDraft, isPrerelease, assets:[.assets[].name], bodyLen:(.body|length)}'
git fetch origin gh-pages && git show origin/gh-pages:appcast.xml | grep -F "OpenUsage-{version}.dmg"
curl -s "https://robinebers.github.io/openusage/appcast.xml" | grep -F "OpenUsage-{version}.dmg"

The second check matters: publishing is two hops — Release (or pricing-supplement) pushes appcast.xml to the gh-pages branch, then .github/workflows/deploy-pages.yml on main deploys that branch to the live site (Pages source is "GitHub Actions", not legacy branch deploy). Auto deploy runs on workflow_run after Release completes; GitHub sometimes returns "Deployment failed, try again later" even though gh-pages is already correct. If the branch has the version but the live URL does not after ~10 minutes, check gh run list --workflow=deploy-pages.yml and re-run gh workflow run deploy-pages.yml --ref main (must use main — the workflow file is not on gh-pages). Sparkle clients only see the live URL.

Require isDraft=false, isPrerelease=true for beta or false for stable, an OpenUsage-<version>.dmg asset, bodyLen>0, and the version present in the appcast. If a draft was left behind, migrate its notes/assets onto the published release, then delete it — but only once a separate PUBLISHED release for the tag already exists:

sh
tag="v{version}"
if [ "$(gh release view "$tag" --json isDraft --jq '.isDraft')" = "false" ]; then
  gh api repos/robinebers/openusage/releases --paginate \
    --jq '.[] | select(.draft and .tag_name=="'"$tag"'") | .id' \
    | xargs -I{} gh api -X DELETE repos/robinebers/openusage/releases/{}
else
  echo "No published release for $tag yet - publish it first; do NOT delete the draft."
fi

Changelog template

Only include category sections that have entries.

markdown
## v{version}

### New Features
- {message} ([#{pr}](https://github.com/robinebers/openusage/pull/{pr})) by @{author}

### Bug Fixes
- {message} ([#{pr}](https://github.com/robinebers/openusage/pull/{pr})) by @{author}

### Refactor
- {message} by @{author}

### Chores
- {message} by @{author}

---

### Changelog
**Full Changelog**: [{prev_tag}...v{version}](https://github.com/robinebers/openusage/compare/{prev_tag}...v{version})

- [{short_hash}](https://github.com/robinebers/openusage/commit/{full_hash}) {commit message} by @{author}

{prev_tag} is the previous release in the same channel: last stable for a stable cut, last beta (or last stable for the first beta in a lane) for a beta cut.

Rules

  • 7-char short commit hashes; tags always prefixed with v.
  • Stable changelogs span last-stable → this-stable (roll up the whole beta series); beta changelogs span previous-tag → this-beta.
  • Never push or tag automatically — ask the owner first.
  • Always publish notes to the GitHub Release — never blank.
  • The version is the tag; never edit version files.
  • The appcast is append-only: older installs and the other channel's latest build must keep working, so the workflow aborts rather than shrink it.

Release secrets and one-time setup live in the README under Release setup.

© robinebers, 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 .agents/skills/release-swift of robinebers/openusage.

Open the folder on GitHubat commit 1c37176

Compare with similar skills

Release Swift 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.

Release Swift compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release Swift this skillrobinebers/openusage4.3k—~1.6kAutomated safety check: PassMIT
Publish Releasefetch-rewards/swift-mocking100—~671Automated safety check: PassMIT
Megaphone ReleaseKuberwastaken/megaphone170—~1.3kAutomated safety check: PassMIT
Create Release Checklistsoftware-mansion/smelter734—~1.9kAutomated safety check: NotesCustom licence
Prepare Releaselnccbrown/HSSM126—~1.2kAutomated safety check: PassCustom licence
Releasef-is-h/Usage4Claude407—~1.9kAutomated safety check: PassMIT

Similar skills

  • Publish Release

    fetch-rewards/swift-mocking

    Publish the draft GitHub release for swift-mocking after the changelog PR has been merged.

    100 GitHub stars~671 tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

  • Megaphone Release

    Kuberwastaken/megaphone

    Prepare, validate, publish, and verify Megaphone releases. An agent skill from Kuberwastaken/megaphone.

    170 GitHub stars~1.3k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

  • Create Release Checklist

    software-mansion/smelter

    Generate a GitHub release-checklist issue for a full (non-RC) release of the Smelter server and/or the TypeScript SDK.

    734 GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check: notes

  • Prepare Release

    lnccbrown/HSSM

    Automate the HSSM pre-release workflow: update changelog, build docs locally, and create a draft GitHub release.

    126 GitHub stars~1.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Release

    f-is-h/Usage4Claude

    发布 Usage4Claude 新版本时使用。当用户说“发布新版本 / 发版 / 出新版 / release / 打 tag 发布 / 准备发版材料”等，用本 skill 引导完成从收集变更、编写 CHANGELOG 与 RELEASENOTES、更新版本号、编译验证，到发版 commit、CI 自动发布的完整流程。

    407 GitHub stars~1.9k tokensUpdated 11 days ago
    DevelopmentAuto-check passed

  • Prepare Release

    fetch-rewards/swift-mocking

    Analyze merged PRs since the last release, determine the next version, update the changelog, open the PR, and populate the draft GitHub release notes for a new swift-mocking release.

    100 GitHub stars~2k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

More from robinebers/openusage

All 25 skills in this repo

  • Swiftui Patterns

    robinebers/openusage

    Best practices and example-driven guidance for building native macOS SwiftUI scenes and components, including windows, commands, toolbars, settings, split views, inspectors, menu bar extras, and…

    4.3k GitHub stars~3.4k tokensUpdated today
    Auto-check passed

  • macOS Telemetry

    robinebers/openusage

    Add and verify lightweight macOS runtime telemetry. An agent skill from robinebers/openusage.

    4.3k GitHub stars~934 tokensUpdated today
    Auto-check passed

  • Telemetry

    robinebers/openusage

    Add lightweight runtime telemetry and debug instrumentation to macOS apps, then verify those events after building and running.

    4.3k GitHub stars~977 tokensUpdated today
    Auto-check passed

  • Window Management

    robinebers/openusage

    Customize macOS 15+ SwiftUI windows and scene behavior using Window, WindowGroup, and macOS window modifiers.

    4.3k GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Appkit Interop

    robinebers/openusage

    Decide when and how to bridge a macOS app from SwiftUI into AppKit.

    4.3k GitHub stars~741 tokensUpdated today
    Auto-check passed

  • Build Run Debug

    robinebers/openusage

    Build, run, and debug local macOS apps and desktop executables using shell-first Xcode and Swift workflows.

    4.3k GitHub stars~1.8k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Release Swift

What does Release Swift do?

Cut a release of OpenUsage (Swift menu-bar app): pick a version, generate a categorized changelog, tag from main, and publish the GitHub Release with notes. Release Swift is an agent skill from robinebers/openusage. Cut a release of OpenUsage (Swift menu-bar app): pick a version, generate a categorized changelog, tag from main, and publish the GitHub Release with notes.

When should I use Release Swift?

Release Swift fits situations like: ship an Early Access beta; A stable release.

How do I install Release Swift in Claude Code?

Run `npx skills add robinebers/openusage --skill release-swift -a claude-code`. Or copy the skill folder (.agents/skills/release-swift in robinebers/openusage) into .claude/skills/release-swift in your project. Claude Code loads it when a task matches its description.

How do I install Release Swift in Codex?

Run `npx skills add robinebers/openusage --skill release-swift -a codex`. Or copy the skill folder (.agents/skills/release-swift in robinebers/openusage) into .agents/skills/release-swift in your project. Codex loads it when a task matches its description.

Can I use Release Swift 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 robinebers/openusage --skill release-swift -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-swift, .gemini/skills/release-swift, .github/skills/release-swift and .opencode/skills/release-swift in your project.

What does Release Swift need to run?

Going by SKILL.md and its folder, Release Swift needs the command-line tools its instructions call (gh, git and curl).

Does Release Swift access the network?

SKILL.md names 1 domain. In commands or code: robinebers.github.io; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Release Swift 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 Swift use?

Release Swift 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 Swift use?

About 1.6k tokens (SKILL.md is roughly 6.6k 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 Swift?

Skills that share tags, products or a category with Release Swift: Publish Release (fetch-rewards/swift-mocking, 100 stars), Megaphone Release (Kuberwastaken/megaphone, 170 stars), Create Release Checklist (software-mansion/smelter, 734 stars) and Prepare Release (lnccbrown/HSSM, 126 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release Swift?

robinebers (a GitHub user) maintains it in robinebers/openusage, which has 4,337 GitHub stars. The repository holds 25 skills in this directory. The repository was last updated on October 10, 2026.

Source: robinebers/openusage on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.