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.
Prepare, validate, publish, and verify Megaphone releases. An agent skill from Kuberwastaken/megaphone.
Install Megaphone Release
$ npx skills add Kuberwastaken/megaphone --skill megaphone-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Kuberwastaken/megaphone megaphone-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/Kuberwastaken/megaphone.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/megaphone-release .claude/skills/megaphone-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 "megaphone-release" agent skill from https://github.com/Kuberwastaken/megaphone/tree/main/.agents/skills/megaphone-release into .claude/skills/megaphone-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "megaphone-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/Kuberwastaken/megaphone/tree/main/.agents/skills/megaphone-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 Kuberwastaken/megaphone --skill megaphone-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Kuberwastaken/megaphone megaphone-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Kuberwastaken/megaphone.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/megaphone-release .agents/skills/megaphone-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 "megaphone-release" agent skill from https://github.com/Kuberwastaken/megaphone/tree/main/.agents/skills/megaphone-release into .agents/skills/megaphone-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "megaphone-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 Kuberwastaken/megaphone --skill megaphone-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Kuberwastaken/megaphone megaphone-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Kuberwastaken/megaphone.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/megaphone-release .cursor/skills/megaphone-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 "megaphone-release" agent skill from https://github.com/Kuberwastaken/megaphone/tree/main/.agents/skills/megaphone-release into .cursor/skills/megaphone-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "megaphone-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/Kuberwastaken/megaphone.git --path .agents/skills/megaphone-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 Kuberwastaken/megaphone --skill megaphone-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Kuberwastaken/megaphone megaphone-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Kuberwastaken/megaphone.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/megaphone-release .gemini/skills/megaphone-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 "megaphone-release" agent skill from https://github.com/Kuberwastaken/megaphone/tree/main/.agents/skills/megaphone-release into .gemini/skills/megaphone-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "megaphone-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 Kuberwastaken/megaphone megaphone-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 Kuberwastaken/megaphone --skill megaphone-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Kuberwastaken/megaphone.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/megaphone-release .github/skills/megaphone-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 "megaphone-release" agent skill from https://github.com/Kuberwastaken/megaphone/tree/main/.agents/skills/megaphone-release into .github/skills/megaphone-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "megaphone-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 Kuberwastaken/megaphone --skill megaphone-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 Kuberwastaken/megaphone megaphone-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Kuberwastaken/megaphone.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/megaphone-release .opencode/skills/megaphone-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 "megaphone-release" agent skill from https://github.com/Kuberwastaken/megaphone/tree/main/.agents/skills/megaphone-release into .opencode/skills/megaphone-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "megaphone-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
megaphone-release- GitHub stars
- 170
- Token cost
- ~1.3k tokens
- SKILL.md length
- 545 words
- Files
- 3 (incl. scripts)
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
Prepare, validate, publish, and verify Megaphone releases. An agent skill from Kuberwastaken/megaphone.
- Works in 7 steps: Inspect the repository and fetch the… → Use the newest stable semver tag… → Choose the next version → …
- The user asks to release Megaphone
- SKILL.md covers Guardrails, Prepare a stable release, Publish and Verify the shipped release, plus 1 more section
- Runs Shell scripts from its folder; calls git and make; reaches megaphone.kuber.studio
What it does
Megaphone Release is an agent skill from Kuberwastaken/megaphone. Prepare, validate, publish, and verify Megaphone releases. Use when the user asks to release Megaphone, choose or bump its version, update release notes, validate release readiness, create a stable vX.Y.Z tag, inspect the moving Dev release, publish Megaphone.dmg, verify updater compatibility, or confirm that megaphone.kuber.studio reflects the latest GitHub release.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `agents/openai.yaml` and `scripts/megaphone-release-check.sh`).
It sits in Development, covering Changelog and release notes, Feature launches and release readiness and Text to speech and voice. It works with GitHub and macOS. The repository describes itself as: Free, private, on-device dictation for Mac, powered by Apple's SpeechAnalyzer and Foundation Models. The licence is MIT.
When your agent uses it
- The user asks to release Megaphone
- Bump its version
- Update release notes
- Validate release readiness
Example prompts
- “/megaphone-release”
Requirements
- A Bash shell
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Inspect the repository and fetch the Megaphone remote
- Use the newest stable semver tag reachable from the release branch as the comparison boundary. Inspect both merge-level and individual…
- Choose the next version
- Update both version keys in Info.plist to the target version
- Add the target section above the previous release in CHANGELOG.md. Describe everything user-visible since the previous tag, including…
- Validate on the companion Mac because Megaphone requires the macOS 26 SDK
- Commit the prep as Prepare v release. Show the exact changelog and version diff to the user before tagging.
What it can do on your machine
Read from SKILL.md and the folder at commit 5a9136b. 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
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
gitmake
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:
megaphone.kuber.studio
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
Megaphone Release loads about 1.3k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 545 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); the scripts in this folder are not scanned.
SKILL.md
The full file from Kuberwastaken/megaphone at commit 5a9136b, republished under its MIT licence (© Kuberwastaken). 545 words, ~1,346 tokens.
Download SKILL.mdSave it as
.claude/skills/megaphone-release/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- megaphone-release
- description
- Prepare, validate, publish, and verify Megaphone releases. Use when the user asks to release Megaphone, choose or bump its version, update release notes, validate release readiness, create a stable vX.Y.Z tag, inspect the moving Dev release, publish Megaphone.dmg, verify updater compatibility, or confirm that megaphone.kuber.studio reflects the latest GitHub release.
Megaphone Release
Release Megaphone through its tag-driven GitHub Actions pipeline. Treat CHANGELOG.md as the stable release-notes source. A vX.Y.Z tag builds Megaphone.dmg, optionally signs and notarizes it, publishes the stable GitHub release, and asks the Pages workflow to hydrate the website with that release. Each push to main separately replaces the dev prerelease and Megaphone-Dev.dmg.
Guardrails
- Work only in
Kuberwastaken/megaphone. Do not infer repository identity from a remote namedorigin; inherited clones may still use that name for FreeFlow. - Preserve unrelated changes and never use destructive cleanup.
- Keep sequential release-prep commits. Stage only deliberate files.
- Do not push a branch or tag, publish a release, or move the
devtag without explicit user authorization. - Require explicit confirmation of the stable version and changelog before tagging.
- Do not hand-build and upload a stable DMG. The tagged workflow is the source of truth.
- Never expose signing or notarization secrets. Confirm only whether required GitHub secrets are configured through workflow behavior.
Prepare a stable release
Inspect the repository and fetch the Megaphone remote:
bash git status --short --branch git remote -v git fetch <megaphone-remote> --tags --prune git tag --list 'v[0-9]*.[0-9]*.[0-9]*' --sort=-version:refnameChoose
<megaphone-remote>by matching its URL toKuberwastaken/megaphone, not by its name. Stop if the worktree contains substantial unrelated work.Use the newest stable semver tag reachable from the release branch as the comparison boundary. Inspect both merge-level and individual history:
bash git log --first-parent --reverse --oneline <previous-tag>..HEAD git log --reverse --oneline <previous-tag>..HEAD git diff --stat <previous-tag>..HEAD git diff --name-status <previous-tag>..HEADChoose the next version:
- Patch: fixes, reliability, polish, or small compatible improvements.
- Minor: a notable new user-facing capability.
- Major: breaking behavior or compatibility.
Update both version keys in
Info.plistto the target version:CFBundleShortVersionStringCFBundleVersion
The workflow stamps them again, but keeping source synchronized makes Dev builds, About, and the next release proposal accurate.
Add the target section above the previous release in
CHANGELOG.md. Describe everything user-visible since the previous tag, including merged work that predates the prep commit. Use only relevant headings amongAdded,Changed,Improved, andFixed. Avoid commit hashes, internal implementation narration, and claims not supported by the diff.Validate on the companion Mac because Megaphone requires the macOS 26 SDK:
bash .agents/skills/megaphone-release/scripts/megaphone-release-check.sh <version> git diff --check make clean make test make ARCH="$(uname -m)" APP_NAME="Megaphone Dev" BUNDLE_ID=studio.kuber.megaphone.dev CODESIGN_IDENTITY=- codesign --verify --deep --strict "build/Megaphone Dev.app"Commit the prep as
Prepare v<version> release. Show the exact changelog and version diff to the user before tagging.
Show full SKILL.md (194 more words)Show less
Publish
After explicit approval:
git push <megaphone-remote> <release-branch>:main
git tag -a v<version> -m "Megaphone v<version>"
git push <megaphone-remote> v<version>Do not tag a commit that is not on Megaphone’s remote main. Watch .github/workflows/release.yml through completion.
Verify the shipped release
Confirm all of the following:
- GitHub Release
v<version>is published, stable, and marked latest. - Its only expected app artifact is
Megaphone.dmg; the asset is non-empty and downloadable. - Release notes came from the matching changelog section and include the macOS 26 requirement.
- The workflow ran tests, built the universal app, and completed the configured signing/notarization path.
- The DMG contains
Megaphone.appwith version<version>and bundle IDcom.kuberwastaken.megaphone. UpdateManagercan see the semantic release and locate the.dmgasset. When practical, test update discovery from the previous installed stable version.- The Pages workflow completes and
https://megaphone.kuber.studioshows the same stable version and download URL. - The moving
devprerelease remains separate and is not marked latest.
If any verification fails, do not silently retag or replace a stable release. Diagnose the failed stage and ask before mutating published state.
Helper
Run .agents/skills/megaphone-release/scripts/megaphone-release-check.sh <version> after preparing Info.plist and CHANGELOG.md. It checks repository identity, semver and tag availability, synchronized source versions, changelog extraction, Megaphone artifact names, workflow triggers, updater wiring, website hydration, and release ancestry.
© Kuberwastaken, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (scripts) in .agents/skills/megaphone-release of Kuberwastaken/megaphone.
- SKILL.md
- agents/openai.yaml
- scripts/megaphone-release-check.sh
Open the folder on GitHubat commit 5a9136b
Compare with similar skills
Megaphone 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 |
|---|---|---|---|---|---|---|
| Megaphone Release this skillKuberwastaken/megaphone | 170 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Create Release Checklistsoftware-mansion/smelter | 734 | — | ~1.9k | Automated safety check: Notes | Custom licence | |
| Release MaintainerUndertone0809/rudder | 292 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Mole CLI Release Flowtw93/Mole | 70k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Releaseeugene1g/agent-safehouse | 2.1k | — | ~3.5k | Automated safety check: Pass | Apache-2.0 | |
| Release Swiftrobinebers/openusage | 4.3k | — | ~1.6k | Automated safety check: Pass | MIT |
Similar skills
Release Maintainer
Undertone0809/rudder
A skill your agent uses when inspecting, preparing, executing, recovering, or verifying Rudder releases across npm, GitHub Releases, Desktop assets, tags, dist-tags, changelogs, Discord…
Mole CLI Release Flow
tw93/Mole
Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.
Release
eugene1g/agent-safehouse
Run the local Agent Safehouse release flow: inspect commits since the last published release, propose the next SemVer version and changelog, present a dry-run for confirmation, then update…
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.
Prepare Release
lnccbrown/HSSM
Automate the HSSM pre-release workflow: update changelog, build docs locally, and create a draft GitHub release.
Related
Questions about Megaphone Release
What does Megaphone Release do?
Prepare, validate, publish, and verify Megaphone releases. An agent skill from Kuberwastaken/megaphone. Megaphone Release is an agent skill from Kuberwastaken/megaphone. Prepare, validate, publish, and verify Megaphone releases.
When should I use Megaphone Release?
Megaphone Release fits situations like: the user asks to release Megaphone; bump its version; update release notes; validate release readiness.
How do I install Megaphone Release in Claude Code?
Run `npx skills add Kuberwastaken/megaphone --skill megaphone-release -a claude-code`. Or copy the skill folder (.agents/skills/megaphone-release in Kuberwastaken/megaphone) into .claude/skills/megaphone-release in your project. Claude Code loads it when a task matches its description.
How do I install Megaphone Release in Codex?
Run `npx skills add Kuberwastaken/megaphone --skill megaphone-release -a codex`. Or copy the skill folder (.agents/skills/megaphone-release in Kuberwastaken/megaphone) into .agents/skills/megaphone-release in your project. Codex loads it when a task matches its description.
Can I use Megaphone 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 Kuberwastaken/megaphone --skill megaphone-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/megaphone-release, .gemini/skills/megaphone-release, .github/skills/megaphone-release and .opencode/skills/megaphone-release in your project.
What does Megaphone Release need to run?
Going by SKILL.md and its folder, Megaphone Release needs a shell for the scripts in its folder and the command-line tools its instructions call (git and make). Our summary lists: A Bash shell.
Does Megaphone Release access the network?
SKILL.md names 1 domain. In commands or code: megaphone.kuber.studio; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Megaphone 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Megaphone Release use?
Megaphone 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 Megaphone Release use?
About 1.3k tokens (SKILL.md is roughly 5.4k 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 Megaphone Release?
Skills that share tags, products or a category with Megaphone Release: Create Release Checklist (software-mansion/smelter, 734 stars), Release Maintainer (Undertone0809/rudder, 292 stars), Mole CLI Release Flow (tw93/Mole, 70k stars) and Release (eugene1g/agent-safehouse, 2.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Megaphone Release?
Kuberwastaken (a GitHub user) maintains it in Kuberwastaken/megaphone, which has 170 GitHub stars. The repository was last updated on July 24, 2026.
Source: Kuberwastaken/megaphone on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.