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.
Generate GitHub release notes for unreleased CleverSwitch tags in the established repo format.
Install Release Notes
$ npx skills add MikalaiBarysevich/CleverSwitch --skill release-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install MikalaiBarysevich/CleverSwitch release-notes --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/MikalaiBarysevich/CleverSwitch.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release-notes .claude/skills/release-notes && 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 "release-notes" agent skill from https://github.com/MikalaiBarysevich/CleverSwitch/tree/main/.claude/skills/release-notes into .claude/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", 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/MikalaiBarysevich/CleverSwitch/tree/main/.claude/skills/release-notesType 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 MikalaiBarysevich/CleverSwitch --skill release-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install MikalaiBarysevich/CleverSwitch release-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MikalaiBarysevich/CleverSwitch.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/release-notes .agents/skills/release-notes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "release-notes" agent skill from https://github.com/MikalaiBarysevich/CleverSwitch/tree/main/.claude/skills/release-notes into .agents/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", 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 MikalaiBarysevich/CleverSwitch --skill release-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install MikalaiBarysevich/CleverSwitch release-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MikalaiBarysevich/CleverSwitch.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/release-notes .cursor/skills/release-notes && 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 "release-notes" agent skill from https://github.com/MikalaiBarysevich/CleverSwitch/tree/main/.claude/skills/release-notes into .cursor/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", 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/MikalaiBarysevich/CleverSwitch.git --path .claude/skills/release-notes--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 MikalaiBarysevich/CleverSwitch --skill release-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install MikalaiBarysevich/CleverSwitch release-notes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MikalaiBarysevich/CleverSwitch.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/release-notes .gemini/skills/release-notes && 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 "release-notes" agent skill from https://github.com/MikalaiBarysevich/CleverSwitch/tree/main/.claude/skills/release-notes into .gemini/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", 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 MikalaiBarysevich/CleverSwitch release-notesInstalls 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 MikalaiBarysevich/CleverSwitch --skill release-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/MikalaiBarysevich/CleverSwitch.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/release-notes .github/skills/release-notes && 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 "release-notes" agent skill from https://github.com/MikalaiBarysevich/CleverSwitch/tree/main/.claude/skills/release-notes into .github/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", 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 MikalaiBarysevich/CleverSwitch --skill release-notes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install MikalaiBarysevich/CleverSwitch release-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/MikalaiBarysevich/CleverSwitch.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/release-notes .opencode/skills/release-notes && 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 "release-notes" agent skill from https://github.com/MikalaiBarysevich/CleverSwitch/tree/main/.claude/skills/release-notes into .opencode/skills/release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release-notes", 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
release-notes- GitHub stars
- 116
- Token cost
- ~975 tokens
- SKILL.md length
- 300 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- GPL-3.0
At a glance
Generate GitHub release notes for unreleased CleverSwitch tags in the established repo format.
- Works in 5 steps: Find the version range → Extract the format from a recent release → Gather commits and PR context → …
- The user asks to write
- SKILL.md covers Rules and Steps
- Calls git and gh
What it does
Release Notes is an agent skill from MikalaiBarysevich/CleverSwitch. Generate GitHub release notes for unreleased CleverSwitch tags in the established repo format. Use when the user asks to write, draft, prepare, or generate release notes / a release description for CleverSwitch versions.
Its SKILL.md is about 980 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 Changelog and release notes. It works with GitHub, Linux and macOS. The repository describes itself as: A CLI tool to synchronize host switching across multiple Logitech devices. The licence is GPL-3.0.
When your agent uses it
- The user asks to write
- Generate release notes / a release description for CleverSwitch versions
Example prompts
- “/release-notes”
Workflow steps
5 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 de0a4f4. 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
Release Notes loads about 975 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 300 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 MikalaiBarysevich/CleverSwitch at commit de0a4f4, republished under its GPL-3.0 licence (© MikalaiBarysevich). 300 words, ~975 tokens.
Download SKILL.mdSave it as
.claude/skills/release-notes/SKILL.md (or your agent's skills folder).- name
- release-notes
- description
- Generate GitHub release notes for unreleased CleverSwitch tags in the established repo format. Use when the user asks to write, draft, prepare, or generate release notes / a release description for CleverSwitch versions.
CleverSwitch Release Notes
Produce a single combined release-notes markdown body covering every unreleased tag, in the exact format used by prior releases at https://github.com/MikalaiBarysevich/CleverSwitch/releases.
Rules
- One release, not many. If multiple unreleased tags exist (e.g.
v1.2.1andv1.2.2), combine all their changes into a single release-notes body (the release will be cut against the latest tag). Never produce one block per intermediate tag. - Skip already-published tags. Check
gh release listand exclude any tag that already has a published (non-draft) release. - Output a single fenced ```markdown code block containing the raw markdown — no surrounding commentary, no extra prose, ready to paste into the GitHub release editor.
- Do not invent changes. Every bullet must trace back to a real commit/PR in the version range. If a PR has no body, infer the change from the diff (
git show --stat <sha>+ targetedgit show <sha> -- <path>).
Steps
1. Find the version range
git tag -l | sort -V # all tags
gh release list --repo MikalaiBarysevich/CleverSwitch --limit 20 # which are publishedThe range is <latest published tag>..<latest tag>. Tags inside that range are the unreleased ones to document.
2. Extract the format from a recent release
gh release view <recent-published-tag> --repo MikalaiBarysevich/CleverSwitchUse the most recent published release as the canonical format template. Match its section structure, heading levels, bullet style, and bold-label convention exactly.
3. Gather commits and PR context
git log <prev-tag>..<new-tag> --oneline # for each unreleased version
gh pr view <num> --repo MikalaiBarysevich/CleverSwitch # for each PR referenced in commits
git show <sha> --stat # what files changed
git show <sha> -- <path> # actual diff when PR body is emptyTrivial sync/merge commits with no user-facing impact (e.g. "Sync main") are omitted.
4. Write the body
Required structure (copied from prior releases — keep verbatim except for the Overview/Changes content):
### Overview
<one short paragraph: what the release accomplishes from the user's perspective>
### Changes
* **<Short title>:** <what changed and the user-facing impact. Include the technical mechanism only when it explains why the fix matters (e.g. "the `::` form was being parsed as a label and breaking variable expansion").>
* ...
### Platform Support
* **Windows x64**
* **Linux.**
* **macOS.**
### Installation & Assets
* **Windows:** download `cleverswitch_windows_x64.zip` from the **Assets** section below and follow the `Installation.md` included in the archive.
* **Linux:** download `cleverswitch_linux.tar.gz` from the **Assets** section below and follow the `Installation.md` included in the archive.
* **macOS:** download `cleverswitch_macOS.tar.gz` from the **Assets** section below and follow the `Installation.md` included in the archive.5. Style notes
- Bullet form:
* **Title:** description.— always bold the leading title, always end with a period. - Code identifiers (file names, class names, flags, byte values) go in backticks:
setup_startup_windows.bat,KEY_FLAG_ANALYTICS,0x00. - Order bullets by user-visible importance, not by merge order.
- Overview is one paragraph, two sentences max — name the headline change first.
- Never mention PR numbers, commit SHAs, or internal refactors that have no user impact.
© MikalaiBarysevich, GPL-3.0. 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/release-notes of MikalaiBarysevich/CleverSwitch.
Open the folder on GitHubat commit de0a4f4
Compare with similar skills
Release Notes 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 |
|---|---|---|---|---|---|---|
| Release Notes this skillMikalaiBarysevich/CleverSwitch | 116 | — | ~975 | Automated safety check: Pass | GPL-3.0 | |
| Mole CLI Release Flowtw93/Mole | 70k | — | ~2.5k | Automated safety check: Pass | GPL-3.0 | |
| Cut Releasejfernandez/bpftop | 2.7k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Releaseeugene1g/agent-safehouse | 2.1k | — | ~3.5k | Automated safety check: Pass | Apache-2.0 | |
| Megaphone ReleaseKuberwastaken/megaphone | 169 | — | ~1.3k | Automated safety check: Pass | MIT | |
| Prepare Releaseneetly/figma-agent-linux | 395 | — | ~833 | Automated safety check: Pass | MIT |
Similar skills
Cut Release
jfernandez/bpftop
Cut a new versioned release of bpftop — pick the version, open a version-bump PR, sign-tag the merge commit on main, and draft GitHub release notes in the project's established format.
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…
Megaphone Release
Kuberwastaken/megaphone
Prepare, validate, publish, and verify Megaphone releases. An agent skill from Kuberwastaken/megaphone.
Prepare Release
neetly/figma-agent-linux
Prepare a new figma-agent-linux release by updating the package version, changelog, and release links, then validating the changes.
GitHub Activity Analyzer
changkun/dotfiles
Comprehensive GitHub contribution analysis for any time period.
More from MikalaiBarysevich/CleverSwitch
Update Claude Md
MikalaiBarysevich/CleverSwitch
Analyze all changes in the current git branch and update CLAUDE.md if architectural or important changes warrant it.
Related
Categories
Questions about Release Notes
What does Release Notes do?
Generate GitHub release notes for unreleased CleverSwitch tags in the established repo format. Release Notes is an agent skill from MikalaiBarysevich/CleverSwitch. Generate GitHub release notes for unreleased CleverSwitch tags in the established repo format.
When should I use Release Notes?
Release Notes fits situations like: the user asks to write; generate release notes / a release description for CleverSwitch versions.
How do I install Release Notes in Claude Code?
Run `npx skills add MikalaiBarysevich/CleverSwitch --skill release-notes -a claude-code`. Or copy the skill folder (.claude/skills/release-notes in MikalaiBarysevich/CleverSwitch) into .claude/skills/release-notes in your project. Claude Code loads it when a task matches its description.
How do I install Release Notes in Codex?
Run `npx skills add MikalaiBarysevich/CleverSwitch --skill release-notes -a codex`. Or copy the skill folder (.claude/skills/release-notes in MikalaiBarysevich/CleverSwitch) into .agents/skills/release-notes in your project. Codex loads it when a task matches its description.
Can I use Release Notes 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 MikalaiBarysevich/CleverSwitch --skill release-notes -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-notes, .gemini/skills/release-notes, .github/skills/release-notes and .opencode/skills/release-notes in your project.
What does Release Notes need to run?
Going by SKILL.md and its folder, Release Notes needs the command-line tools its instructions call (git and gh).
Does Release Notes 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 Release Notes 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 Notes use?
Release Notes is published under the GPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Release Notes use?
About 975 tokens (SKILL.md is roughly 3.9k 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 Notes?
Skills that share tags, products or a category with Release Notes: Mole CLI Release Flow (tw93/Mole, 70k stars), Cut Release (jfernandez/bpftop, 2.7k stars), Release (eugene1g/agent-safehouse, 2.1k stars) and Megaphone Release (Kuberwastaken/megaphone, 169 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Notes?
MikalaiBarysevich (a GitHub user) maintains it in MikalaiBarysevich/CleverSwitch, which has 116 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 5, 2026.
Source: MikalaiBarysevich/CleverSwitch on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.