Release Swift
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.
Publish the draft GitHub release for swift-mocking after the changelog PR has been merged.
Install Publish Release
$ npx skills add fetch-rewards/swift-mocking --skill publish-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install fetch-rewards/swift-mocking publish-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/fetch-rewards/swift-mocking.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/publish-release .claude/skills/publish-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 "publish-release" agent skill from https://github.com/fetch-rewards/swift-mocking/tree/main/.claude/skills/publish-release into .claude/skills/publish-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-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/fetch-rewards/swift-mocking/tree/main/.claude/skills/publish-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 fetch-rewards/swift-mocking --skill publish-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install fetch-rewards/swift-mocking publish-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fetch-rewards/swift-mocking.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/publish-release .agents/skills/publish-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 "publish-release" agent skill from https://github.com/fetch-rewards/swift-mocking/tree/main/.claude/skills/publish-release into .agents/skills/publish-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-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 fetch-rewards/swift-mocking --skill publish-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install fetch-rewards/swift-mocking publish-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fetch-rewards/swift-mocking.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/publish-release .cursor/skills/publish-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 "publish-release" agent skill from https://github.com/fetch-rewards/swift-mocking/tree/main/.claude/skills/publish-release into .cursor/skills/publish-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-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/fetch-rewards/swift-mocking.git --path .claude/skills/publish-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 fetch-rewards/swift-mocking --skill publish-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install fetch-rewards/swift-mocking publish-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fetch-rewards/swift-mocking.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/publish-release .gemini/skills/publish-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 "publish-release" agent skill from https://github.com/fetch-rewards/swift-mocking/tree/main/.claude/skills/publish-release into .gemini/skills/publish-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-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 fetch-rewards/swift-mocking publish-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 fetch-rewards/swift-mocking --skill publish-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/fetch-rewards/swift-mocking.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/publish-release .github/skills/publish-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 "publish-release" agent skill from https://github.com/fetch-rewards/swift-mocking/tree/main/.claude/skills/publish-release into .github/skills/publish-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-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 fetch-rewards/swift-mocking --skill publish-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 fetch-rewards/swift-mocking publish-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/fetch-rewards/swift-mocking.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/publish-release .opencode/skills/publish-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 "publish-release" agent skill from https://github.com/fetch-rewards/swift-mocking/tree/main/.claude/skills/publish-release into .opencode/skills/publish-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-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
publish-release- GitHub stars
- 100
- Token cost
- ~671 tokens
- SKILL.md length
- 276 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
Publish the draft GitHub release for swift-mocking after the changelog PR has been merged.
- Works in 4 steps: Identify the draft release → Validate the changelog is in place → Publish the release → …
- Tasks that involve iOS development
- SKILL.md covers 1. Identify the draft release, 2. Validate the changelog is…, 3. Publish the release and 4. Confirm
- Calls git and gh
What it does
Publish Release is an agent skill from fetch-rewards/swift-mocking. Publish the draft GitHub release for swift-mocking after the changelog PR has been merged. Creates the git tag and makes the release public. Run only after /prepare-release and the changelog PR is merged.
Its SKILL.md is about 670 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 and Changelog and release notes. It works with Git and GitHub. The repository describes itself as: Swift macros for generating mocks. The licence is MIT.
When your agent uses it
- Tasks that involve iOS development
- Tasks that involve Changelog and release notes
Example prompts
- “/publish-release”
Workflow steps
4 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 762fdd1. 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
Publish Release loads about 671 tokens when it runs. Until then it costs about 55 tokens; SKILL.md has 276 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 fetch-rewards/swift-mocking at commit 762fdd1, republished under its MIT licence (© fetch-rewards). 276 words, ~671 tokens.
Download SKILL.mdSave it as
.claude/skills/publish-release/SKILL.md (or your agent's skills folder).- name
- publish-release
- description
- Publish the draft GitHub release for swift-mocking after the changelog PR has been merged. Creates the git tag and makes the release public. Run only after /prepare-release and the changelog PR is merged.
Publish Release
Publishes the draft GitHub release prepared by /prepare-release. Run this after the changelog PR is merged.
1. Identify the draft release
gh release list --repo fetch-rewards/swift-mockingIf a draft exists: note its version (e.g. 0.3.0) and continue to step 2.
If no draft exists: fetch main and check whether the topmost (most recent) version entry in CHANGELOG.md has a corresponding git tag:
git fetch origin
git show origin/main:CHANGELOG.md
git tag --sort=-version:refnameOnly look at the single topmost version in CHANGELOG.md. If that version has no corresponding git tag (i.e. the changelog PR merged but the draft was lost), recreate the draft. Extract the release notes from that version's section — everything between its header and the next version's header, excluding the version header line itself. The assembled notes body looks like:
### ✨ Features
- Example entry ([#NNN](https://github.com/fetch-rewards/swift-mocking/pull/NNN))
[Full Changelog](https://github.com/fetch-rewards/swift-mocking/compare/<previous_version>...<version>)where <previous_version> is the version entry directly below it in CHANGELOG.md. The extracted content already ends with a blank line; append just the full-changelog link directly. Write the assembled body to a temp file and create the draft:
gh release create <version> --repo fetch-rewards/swift-mocking --draft --title "Version <version>" --notes-file <path>The draft is now recreated. Continue to step 2 using the <version> just determined from CHANGELOG.md.
If the topmost CHANGELOG.md version already has a corresponding git tag (i.e. it is already released), stop and tell the user to run /prepare-release first.
2. Validate the changelog is in place
Fetch the latest main and check that CHANGELOG.md contains a version entry matching the draft release version:
git fetch origin
git show origin/main:CHANGELOG.md | grep "Version <version>"If the version is not found, stop and tell the user the changelog PR for <version> has not been merged into main yet.
3. Publish the release
gh release edit <version> --repo fetch-rewards/swift-mocking --draft=falseThis creates the <version> git tag pointing to the current HEAD of main and makes the release public.
4. Confirm
Report the published release URL to the user.
© fetch-rewards, 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/publish-release of fetch-rewards/swift-mocking.
Open the folder on GitHubat commit 762fdd1
Compare with similar skills
Publish 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 |
|---|---|---|---|---|---|---|
| Publish Release this skillfetch-rewards/swift-mocking | 100 | — | ~671 | Automated safety check: Pass | MIT | |
| Release Swiftrobinebers/openusage | 4.3k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Kt Search Releasejillesvangurp/kt-search | 155 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Draft Release Notesjamiepine/voicebox | 57k | — | ~941 | Automated safety check: Pass | MIT | |
| Mole Release Notes Publishertw93/Mole | 70k | — | ~1.9k | Automated safety check: Pass | GPL-3.0 | |
| Release Bumpjamiepine/voicebox | 57k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
Kt Search Release
jillesvangurp/kt-search
A skill your agent uses when the user wants to cut, publish, tag, or create a GitHub release for kt-search, especially when the task includes version bumping, validating that commits are pushed…
Draft Release Notes
jamiepine/voicebox
Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.
Mole Release Notes Publisher
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
Release Bump
jamiepine/voicebox
Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.
Verdaccio Pull Request Workflow
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
More from fetch-rewards/swift-mocking
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.
Related
Categories
Questions about Publish Release
What does Publish Release do?
Publish the draft GitHub release for swift-mocking after the changelog PR has been merged. Publish Release is an agent skill from fetch-rewards/swift-mocking. Publish the draft GitHub release for swift-mocking after the changelog PR has been merged.
When should I use Publish Release?
Publish Release fits situations like: tasks that involve iOS development; tasks that involve Changelog and release notes.
How do I install Publish Release in Claude Code?
Run `npx skills add fetch-rewards/swift-mocking --skill publish-release -a claude-code`. Or copy the skill folder (.claude/skills/publish-release in fetch-rewards/swift-mocking) into .claude/skills/publish-release in your project. Claude Code loads it when a task matches its description.
How do I install Publish Release in Codex?
Run `npx skills add fetch-rewards/swift-mocking --skill publish-release -a codex`. Or copy the skill folder (.claude/skills/publish-release in fetch-rewards/swift-mocking) into .agents/skills/publish-release in your project. Codex loads it when a task matches its description.
Can I use Publish 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 fetch-rewards/swift-mocking --skill publish-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/publish-release, .gemini/skills/publish-release, .github/skills/publish-release and .opencode/skills/publish-release in your project.
What does Publish Release need to run?
Going by SKILL.md and its folder, Publish Release needs the command-line tools its instructions call (git and gh).
Does Publish 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 Publish 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 Publish Release use?
Publish 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 Publish Release use?
About 671 tokens (SKILL.md is roughly 2.7k 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 Publish Release?
Skills that share tags, products or a category with Publish Release: Release Swift (robinebers/openusage, 4.3k stars), Kt Search Release (jillesvangurp/kt-search, 155 stars), Draft Release Notes (jamiepine/voicebox, 57k stars) and Mole Release Notes Publisher (tw93/Mole, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Publish Release?
fetch-rewards (a GitHub organization) maintains it in fetch-rewards/swift-mocking, which has 100 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on July 14, 2026.
Source: fetch-rewards/swift-mocking on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.