# Release Notes > Publish curated release notes for a Mole `V` tag. Encodes the V1.37.0+ bilingual format, the gh release edit (not create) flow, sponsors graphql query, and the six-reaction set. User-only because publishing is a side effect that touches the public release page. - Skill: `justcyl/release-notes` (Agent Skill, multi-file: 3 files) - Install (CLI): `npx skillmds@latest add justcyl/release-notes` - Raw SKILL.md: https://api.skillmd.com/api/skills/justcyl/release-notes/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Integrations & APIs - Author: justcyl (https://skillmd.com/u/justcyl) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/justcyl/release-notes --- # 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 `. 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 any narrowed detection, removed feature, or "controlled regression" wording. Examples that have shipped before: the V1.40 VPN narrowing (37a446c9) silently stopped detecting split-tunnel third-party VPNs, the Bluetooth reset removal (357ee057) dropped a flow some users depended on. These belong in notes even when not bug-fix-shaped, because users will hit them in production and won't know what changed. 5. **Sponsors**. Run `scripts/sponsors.sh` from this skill dir. 6. **Contributors in this range**. `git log ..V --pretty='%an' | sort -u`. Exclude `tw93` and bots. 7. **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 finished — wait, don't `gh release create`. ## Pre-flight (cross-check against CLAUDE.md) These should already be true if the tag was pushed correctly. Confirm before publishing notes: - `grep '^VERSION=' mole` matches ``. - `SECURITY_AUDIT.md` opening line reflects the new version and date. - `./scripts/check.sh --format` clean. - `MOLE_TEST_NO_AUTH=1 MOLE_TEST_JOBS=2 BATS_FORMATTER=tap ./scripts/test.sh` exits 0. - `go test ./cmd/...` and `make build` pass. If any fail, stop. The notes can wait; a bad release tag cannot. ## Format Strictly follow V1.37.0+ shape. Compare against a recent release if unsure: `gh release view V1.37.0 --repo tw93/Mole --json body --jq .body`. Structure: ``` ## What's new in V 1. ****: . 2. ... ## V 更新内容 1. **<中文 headline>**：<一句中文说明>。 2. ... ## Thanks 💖 Sponsors: <@handle1> <@handle2> ... Contributors: <@handle1> <@handle2> ... > Mole · macOS cleanup · https://github.com/tw93/Mole ``` ### Format rules (all are documented bugs that have shipped before) - **No em dash anywhere**. Use commas, periods, colons, semicolons, or parentheses. - **No emoji except the version emoji** in the two section headers and `💖` in the Thanks header. - **No inline PR refs, no inline `@handle` thanks**. PRs and people belong in the closing 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. - **Verify every command mentioned in the notes actually exists in HEAD**. CLAUDE.md cites `mo check / mo doctor` as a case where a removed command nearly shipped as a "feature". - **Pick icons that match the action, not the category**. Broom (🧹) implies "safe to delete" — never use it on rows like iOS Backups, Xcode Archives, Old Downloads where that's a false promise. Eyes (👀) is the safe "look here" choice. ## Publish Once the user approves the draft: ```bash gh release edit V --repo tw93/Mole \ --title "V " \ --notes-file ``` **Never** `gh release create` — it conflicts with the release the workflow already made. Then add the six reactions: `bash scripts/post-reactions.sh V`. ## After publish - `gh release view V --repo tw93/Mole --web` (open in browser) so the user can eyeball it. - Remind the user: Homebrew tap + Homebrew core PR are workflow-driven and should already be in flight; do not re-run them 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. The workflow takes about 2 minutes for an Mn.m.0. - If the user has not given an explicit "publish" / "提交" signal, stop after the draft. ## Helper scripts - `scripts/sponsors.sh` — fetches the 30 most recent sponsors via `gh api graphql`. Uses the minimal query that works on a token without `read:user` scope. - `scripts/post-reactions.sh ` — adds the six reactions (`+1`, `laugh`, `hooray`, `heart`, `rocket`, `eyes`) to the release.