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

Mole Release Notes Publisher

by tw93 in 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.

GPL-3.0Auto-check passedDevelopment

Install Mole Release Notes Publisher

skills CLI
$ npx skills add tw93/Mole --skill release-notes -a claude-code

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

GitHub CLI
$ gh skill install tw93/Mole release-notes --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/tw93/Mole.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release-notes .claude/skills/release-notes && 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-notes
GitHub stars
70k
Token cost
~1.9k tokens
SKILL.md length
933 words
Files
3 (incl. scripts)
Skills in repo
4
Repo updated
First seen
Licence
GPL-3.0

At a glance

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.

  • Works in 6 steps: Version. Capital V, e.g. V1.38.0.… → CodeName + emoji. Ask the user. The… → Release commit range. git log ..V… → …
  • Writing the notes for a Mole release that was just published
  • SKILL.md covers Inputs to gather, Pre-flight (published-tag…, Format and Publish, plus 3 more sections
  • Runs Shell scripts from its folder; calls gh, git and bash; reaches mole.fit and cdn.tw93.fun

What it does

This step runs after the release workflow has created the GitHub Release with its assets but without generated notes, so the notes are added with gh release edit, never gh release create, which would conflict. Before drafting, the agent confirms the version with a capital V, since a lowercase v does not trigger the workflow, asks you for the code name and emoji used in the title, and checks that the release exists with gh release view.

The raw material is the commit range from the previous tag, read through full commit bodies so user-visible behavior changes, such as narrowed detection or removed features, make it into the notes. Thanks go to issue reporters and PR contributors derived from what the release actually contains, not from a date window, checking that each cited issue was completed and fixed there, and excluding maintainers and bots.

Release readiness evidence, including builds, tests, assets and script updates, stays with a separate release-flow skill, and the agent reuses its published-tag evidence. A script, scripts/post-reactions.sh, handles reactions, and the skill is for explicit requests to edit or publish Mole notes only, not for tagging or code review.

When your agent uses it

  • Writing the notes for a Mole release that was just published
  • Adding contributor and issue-reporter thanks to release notes
  • Posting bilingual notes onto an existing GitHub Release

Example prompts

  • “Publish the release notes for V1.38.0 on the existing GitHub Release.”
  • “Draft the Mole release notes from the commits since the previous tag and credit the reporters.”
  • “Verify the V1.38.0 release exists before editing its notes.”

Requirements

  • GitHub CLI (`gh`) with permission to edit releases
  • An existing Mole release created by the release workflow

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Version. Capital V, e.g. V1.38.0. Lowercase v does not trigger the workflow and may indicate a botched tag.
  2. CodeName + emoji. Ask the user. The title format is V .
  3. Release commit range. git log ..V --oneline gives the raw material.
  4. User-visible behavior changes. Scan the full commit message bodies (not just subjects) for narrowed detection, removed features, or…
  5. Issue reporters and PR contributors in this cycle. Derive them from what the release actually contains, never from a date window of closed…
  6. Verify release exists. gh release view V --repo tw93/Mole --json id,name should return non-empty. If it doesn't, the workflow hasn't…

What it can do on your machine

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

    • gh
    • git
    • bash

    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:

    • mole.fit
    • cdn.tw93.fun

    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

Mole Release Notes Publisher loads about 1.9k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 933 words of instructions outside code blocks.

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

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 tw93/Mole at commit 3ff1b70, republished under its GPL-3.0 licence (© tw93). 933 words, ~1,899 tokens.

Download SKILL.mdSave it as .claude/skills/release-notes/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
release-notes
description
Publish curated release notes for an existing Mole `V<version>` tag, including bilingual format, `gh release edit`, contributor thanks, and reactions. Use only when explicitly asked to edit or publish Mole release notes. Not for release readiness, tagging, or code review.
disable-model-invocation
true

Mole release notes

This skill drives the curated-notes step that runs after release.yml has finished. The workflow creates the GitHub Release with assets but with generate_release_notes: false, so notes must be added in a follow-up gh release edit (never gh release create, the release already exists, and create will conflict).

Inputs to gather

Before drafting, confirm:

  1. Version. Capital V, e.g. V1.38.0. Lowercase v does not trigger the workflow and may indicate a botched tag.
  2. CodeName + emoji. Ask the user. The title format is V<version> <CodeName> <emoji>.
  3. Release commit range. git log <previous-tag>..V<version> --oneline gives the raw material.
  4. User-visible behavior changes. Scan the full commit message bodies (not just subjects) for narrowed detection, removed features, or controlled regressions. These belong in notes even when they are not bug-fix-shaped, because users will encounter the changed boundary in production.
  5. Issue reporters and PR contributors in this cycle. Derive them from what the release actually contains, never from a date window of closed issues: git log --format='%an' <prev>..<tag> for contributors, and the issue numbers the range's own commit messages cite for reporters, checking each is state_reason: completed and was fixed here rather than merely referenced as background. A closing window silently pulls in not_planned issues and everything the PREVIOUS release fixed, which is how V1.55.0 nearly shipped 30 names where 8 were real. Keep it short, for example Issue reporters and PR contributors this cycle: @a · @b. Exclude tw93, youxi798 and bots.
  6. Verify release exists. gh release view V<version> --repo tw93/Mole --json id,name should return non-empty. If it doesn't, the workflow hasn't finished, wait, don't gh release create.

Pre-flight (published-tag evidence)

Use the target tag's exact commit and the completed checks and public-asset evidence from release-flow. Reuse that evidence when it still matches the immutable tag; rerun only a missing or failed gate. A build of a newer working tree does not verify the release being described. The full build, test, asset, and script-update gates stay owned by release-flow rather than a second checklist here.

If evidence is missing, complete the applicable release-flow gate before publishing notes. Keep draft work read-only; an existing release object alone is not proof its assets or upgrade path passed.

Format

Strictly follow the current compact release shape. Read the previous published stable release before the target tag as the live format reference. Exclude the candidate release: the workflow may already have made it the latest release with an empty body. Resolve the previous tag first, then read it with gh release view <previous-tag> --repo tw93/Mole --json tagName,body.

Structure:

<div align="center">
  <img src="https://cdn.tw93.fun/pic/cole.png" alt="Mole Logo" width="120" height="120" style="border-radius:50%" />
  <h1 style="margin: 12px 0 6px;">Mole</h1>
  <p><em>Deep clean and optimize your Mac.</em></p>
</div>

### Changelog

1. **<English headline>**: <one-sentence English elaboration>.
2. ...

### 更新日志

1. **<中文 headline>**：<一句中文说明>。
2. ...

### Thanks

Issue reporters and PR contributors this cycle: @handle1 · @handle2.

### Mole Mac App

Prefer a GUI? [Mole Mac App](https://mole.fit/) brings cleaning, app management, maintenance, disk analysis, and live system status into one native app, with review before deletion and a customizable menu bar HUD. It is $19 once, with lifetime updates and a 14-day refund. [Download and try it](https://mole.fit/download). The CLI stays free and open source.

No --- separators between sections, and no trailing repository link; the published pages end on the Mole Mac App line.

Show full SKILL.md (488 more words)Show less
Format rules (all are documented bugs that have shipped before)
  • Body h1 is just Mole. Version, codename, and emoji live only in the --title argument (V<version> <CodeName> <emoji>); repeating them in the body header is redundant and has been explicitly rejected before.
  • No em dash anywhere. Use commas, periods, colons, semicolons, or parentheses.
  • No sponsor list by default. The current public release style thanks issue reporters and PR contributors for this cycle only.
  • No emoji except the version emoji in the release title. Body section headers stay plain, including ### Thanks (the old Thanks 💖 header is gone from the published pages).
  • No inline PR refs, no inline @handle thanks. PRs and people belong in the dedicated Thanks block only.
  • English block first, 中文 block second. Same numbered order in both blocks. Same number of items.
  • Order items by user-perceived impact, not commit chronology. Headline change first; internal safety hardening, performance, and bug fixes follow.
  • Do not describe overview icons that no longer exist. Analyze overview rows are text-only because emoji width and baselines vary across terminals. If icons return later, they must not imply that user data such as iOS Backups, Xcode Archives, or Old Downloads is safe to delete.
  • Verify every command mentioned in the notes actually exists in HEAD. The deleted mo check / mo doctor commands nearly shipped in notes as a "feature" after they were removed.
  • An incident or troubleshooting note is one sentence of symptom plus one command. No cause taxonomy, no command per branch; the user needs the one line that gets them unstuck. Match the previous release's language treatment for that note: if the last release carried it in one language, do not add a second.
  • Keep the Mole Mac App cross-link to one restrained, fact-backed paragraph. Validate the product scope, price, updates, refund window, and download URL against the current homepage before publishing.

Publish

Once the user approves the draft:

bash
gh release edit V<version> --repo tw93/Mole \
  --title "V<version> <CodeName> <emoji>" \
  --notes-file <path-to-draft>

Never gh release create, it conflicts with the release the workflow already made.

Then add the six reactions with this skill's helper (path is relative to this SKILL.md, not the repo-root scripts/): bash "$(dirname <this SKILL.md>)/scripts/post-reactions.sh" V<version>.

After publish

  • gh release view V<version> --repo tw93/Mole --web (open in browser) so the user can eyeball it.
  • Remind the user: the Homebrew Core PR is workflow-driven and should already be in flight; do not re-run it manually unless the workflow log shows a failure.

When NOT to act

This skill is user-invocable only. It must not run unprompted:

  • If the user mentions release notes in passing, draft only; do not call gh release edit.
  • If gh release view shows the release does not exist yet, wait for the workflow; do not create a competing release manually.
  • If the user has not given an explicit "publish" / "提交" signal, stop after the draft.

Helper script

scripts/post-reactions.sh <tag> lives next to this SKILL.md and adds the six reactions (+1, laugh, hooray, heart, rocket, eyes) to the release.

© tw93, 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

SKILL.md and 2 other files (scripts) in .claude/skills/release-notes of tw93/Mole.

  • SKILL.md
  • agents/openai.yaml
  • scripts/post-reactions.sh

Open the folder on GitHubat commit 3ff1b70

Compare with similar skills

Mole Release Notes Publisher 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.

Mole Release Notes Publisher compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Mole Release Notes Publisher this skilltw93/Mole70k—~1.9kAutomated safety check: PassGPL-3.0
Releasejoenandez/spectre164—~6.5kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Draft Release Notesjamiepine/voicebox57k—~941Automated safety check: PassMIT
Release Bumpjamiepine/voicebox57k—~1.1kAutomated safety check: PassMIT
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT

Similar skills

  • Release

    joenandez/spectre

    Switch persistent Spectre installs between this checkout and the public marketplace, deploy the checkout for local testing, or run the full public GitHub marketplace release workflow including…

    164 GitHub stars~6.5k tokensUpdated 5 days ago
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • 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.

    57k GitHub stars~941 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • 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.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • 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.

    18k GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Go-Redis Release Preparation

    redis/go-redis

    Official

    Prepares a go-redis release locally: picks the next semver, gathers merged PRs, writes the RELEASE-NOTES entry and bumps versions, without publishing.

    22k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

More from tw93/Mole

  • Mole Bug Patterns

    tw93/Mole

    A catalog of recurring bug shapes in the Mole Mac cleaner, used to review safety-sensitive diffs for deletion safety, unbounded commands, shell traps and weak tests.

    70k GitHub stars~2k tokensUpdated today
    Auto-check passed

  • 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.

    70k GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Mole Mac Cleanup CLI Safety

    tw93/Mole

    Teaches an agent to drive the Mole (mo) Mac cleaning CLI safely: preview first, use JSON output, and leave destructive runs to the user.

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

Works with

Categories

Questions about Mole Release Notes Publisher

What does Mole Release Notes Publisher do?

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. This step runs after the release workflow has created the GitHub Release with its assets but without generated notes, so the notes are added with gh release edit, never gh release create, which would conflict. Before drafting, the agent confirms the version with a capital V, since a lowercase v does not trigger the workflow, asks you for the code name and emoji used in the title, and checks that the release exists with gh release view.

When should I use Mole Release Notes Publisher?

Mole Release Notes Publisher fits situations like: writing the notes for a Mole release that was just published; adding contributor and issue-reporter thanks to release notes; posting bilingual notes onto an existing GitHub Release.

How do I install Mole Release Notes Publisher in Claude Code?

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

How do I install Mole Release Notes Publisher in Codex?

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

Can I use Mole Release Notes Publisher 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 tw93/Mole --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 Mole Release Notes Publisher need to run?

Going by SKILL.md and its folder, Mole Release Notes Publisher needs a shell for the scripts in its folder and the command-line tools its instructions call (gh, git and bash). Our summary lists: GitHub CLI (`gh`) with permission to edit releases; An existing Mole release created by the release workflow.

Does Mole Release Notes Publisher access the network?

SKILL.md names 2 domains. In commands or code: mole.fit and cdn.tw93.fun; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Mole Release Notes Publisher 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 Mole Release Notes Publisher use?

Mole Release Notes Publisher 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 Mole Release Notes Publisher use?

About 1.9k tokens (SKILL.md is roughly 7.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 Mole Release Notes Publisher?

Skills that share tags, products or a category with Mole Release Notes Publisher: Release (joenandez/spectre, 164 stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Draft Release Notes (jamiepine/voicebox, 57k stars) and Release Bump (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Mole Release Notes Publisher?

tw93 (a GitHub user) maintains it in tw93/Mole, which has 69,589 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 8, 2026.

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