Release
pwrdrvr/openclaw-codex-app-server
Plan and publish a GitHub Release in a tag-driven repository.
A skill your agent uses when drafting GitHub release notes or changelog content for this project (Genshin Impact Wish Gacha Analyzer).
Install Writing Release Notes
$ npx skills add GoneTone/genshin-impact-wish-gacha-analyzer --skill writing-release-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install GoneTone/genshin-impact-wish-gacha-analyzer writing-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/GoneTone/genshin-impact-wish-gacha-analyzer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/writing-release-notes .claude/skills/writing-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 "writing-release-notes" agent skill from https://github.com/GoneTone/genshin-impact-wish-gacha-analyzer/tree/master/.claude/skills/writing-release-notes into .claude/skills/writing-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-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/GoneTone/genshin-impact-wish-gacha-analyzer/tree/master/.claude/skills/writing-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 GoneTone/genshin-impact-wish-gacha-analyzer --skill writing-release-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install GoneTone/genshin-impact-wish-gacha-analyzer writing-release-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GoneTone/genshin-impact-wish-gacha-analyzer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/writing-release-notes .agents/skills/writing-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 "writing-release-notes" agent skill from https://github.com/GoneTone/genshin-impact-wish-gacha-analyzer/tree/master/.claude/skills/writing-release-notes into .agents/skills/writing-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-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 GoneTone/genshin-impact-wish-gacha-analyzer --skill writing-release-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install GoneTone/genshin-impact-wish-gacha-analyzer writing-release-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GoneTone/genshin-impact-wish-gacha-analyzer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/writing-release-notes .cursor/skills/writing-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 "writing-release-notes" agent skill from https://github.com/GoneTone/genshin-impact-wish-gacha-analyzer/tree/master/.claude/skills/writing-release-notes into .cursor/skills/writing-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-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/GoneTone/genshin-impact-wish-gacha-analyzer.git --path .claude/skills/writing-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 GoneTone/genshin-impact-wish-gacha-analyzer --skill writing-release-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install GoneTone/genshin-impact-wish-gacha-analyzer writing-release-notes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GoneTone/genshin-impact-wish-gacha-analyzer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/writing-release-notes .gemini/skills/writing-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 "writing-release-notes" agent skill from https://github.com/GoneTone/genshin-impact-wish-gacha-analyzer/tree/master/.claude/skills/writing-release-notes into .gemini/skills/writing-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-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 GoneTone/genshin-impact-wish-gacha-analyzer writing-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 GoneTone/genshin-impact-wish-gacha-analyzer --skill writing-release-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/GoneTone/genshin-impact-wish-gacha-analyzer.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/writing-release-notes .github/skills/writing-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 "writing-release-notes" agent skill from https://github.com/GoneTone/genshin-impact-wish-gacha-analyzer/tree/master/.claude/skills/writing-release-notes into .github/skills/writing-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-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 GoneTone/genshin-impact-wish-gacha-analyzer --skill writing-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 GoneTone/genshin-impact-wish-gacha-analyzer writing-release-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GoneTone/genshin-impact-wish-gacha-analyzer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/writing-release-notes .opencode/skills/writing-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 "writing-release-notes" agent skill from https://github.com/GoneTone/genshin-impact-wish-gacha-analyzer/tree/master/.claude/skills/writing-release-notes into .opencode/skills/writing-release-notes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "writing-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
writing-release-notes- GitHub stars
- 152
- Token cost
- ~1.6k tokens
- SKILL.md length
- 340 words
- Files
- 1
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when drafting GitHub release notes or changelog content for this project (Genshin Impact Wish Gacha Analyzer).
- Works in 3 steps: ONE H2：繁中用 ## 此版本重點、英文用 ## What's… → Hero 散文（1–3 段，每段一個主題群） → 過場句 + bullet 區
- Drafting GitHub release notes
- SKILL.md covers 風格摘要, 為什麼這樣寫, 結構（必照） and 取得素材, plus 6 more sections
- Calls git; reaches genshininfo.reh.tw
What it does
Writing Release Notes is an agent skill from GoneTone/genshin-impact-wish-gacha-analyzer. Use when drafting GitHub release notes or changelog content for this project (Genshin Impact Wish Gacha Analyzer). Triggers when the user asks to write release content for a new version, summarize a tag-to-tag diff (e.g. "v1.0.0...v1.1.0"), or produce "更新內容 / 版本說明 / release note". Produces bilingual (zh-Hant on top, en on bottom) Discord-style prose for headline features with a short bullet list for minor items — NOT a corporate-style changelog with one section header per category.
Its SKILL.md is about 1.6k 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 Discord and GitHub. The repository describes itself as: 原神祈願卡池分析 Genshin Impact Wish Gacha Analyzer | A utility for analyzing gacha history, where all data and numbers are well-organized in a convenient manner! The licence is MIT.
When your agent uses it
- Drafting GitHub release notes
- Changelog content for this project (Genshin Impact Wish Gacha Analyzer)
- The user asks to write release content for a new version
- Summarize a tag-to-tag diff (e.g
Example prompts
- “v1.0.0...v1.1.0”
- “更新內容 / 版本說明 / release note”
- “/writing-release-notes”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- ONE H2：繁中用 ## 此版本重點、英文用 ## What's New（不要再切子標題；散文段落自帶轉場）
- Hero 散文（1–3 段，每段一個主題群）
- 過場句 + bullet 區
What it can do on your machine
Read from SKILL.md and the folder at commit 71ecc39. 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:
git
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:
genshininfo.reh.tw
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
Writing Release Notes loads about 1.6k tokens when it runs. Until then it costs about 127 tokens; SKILL.md has 340 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 GoneTone/genshin-impact-wish-gacha-analyzer at commit 71ecc39, republished under its MIT licence (© GoneTone). 340 words, ~1,637 tokens.
Download SKILL.mdSave it as
.claude/skills/writing-release-notes/SKILL.md (or your agent's skills folder).- name
- writing-release-notes
- description
- Use when drafting GitHub release notes or changelog content for this project (Genshin Impact Wish Gacha Analyzer). Triggers when the user asks to write release content for a new version, summarize a tag-to-tag diff (e.g. "v1.0.0...v1.1.0"), or produce "更新內容 / 版本說明 / release note". Produces bilingual (zh-Hant on top, en on bottom) Discord-style prose for headline features with a short bullet list for minor items — NOT a corporate-style changelog with one section header per category.
Writing Release Notes (this project)
風格摘要
雙語輸出：繁體中文在上、英文在下，內容對齊（同樣的 hero 段落數、同樣的 bullet 數、同樣的 emoji 位置）。兩個 H2 直接相鄰，不加 --- 水平線。
每一語言內部：單一 ## 此版本重點 / ## What's New 標題開場，前段用 1–3 段散文敘述主打功能，最後接一段「除此之外，我們還做了：」/「On top of that, we also did:」+ 條列次要項。整體語氣像 Discord 公告，不是 SaaS changelog。
為什麼這樣寫
- 重點功能用散文：可以一邊介紹一邊埋槽點、把使用情境帶出來，讀者比較記得住
- 次要項用 bullet：本來就不需要鋪陳，硬寫散文反而拖
- 不切 H2/H3 per feature：分節會讓 release note 看起來像產品手冊，喪失「聊天感」
結構（必照）
整份輸出順序（兩個 H2 直接相鄰，不加 ---）：
## 此版本重點
（繁中 hero 散文）
（繁中 bullet 區）
## What's New
（英文 hero 散文）
（英文 bullet 區）每一語言內部：
- ONE H2：繁中用
## 此版本重點、英文用## What's New（不要再切子標題；散文段落自帶轉場） - Hero 散文（1–3 段，每段一個主題群）
- 開頭 hook：rhetorical 問題、callback 舊體驗、痛點吐槽——讓讀者一秒進入情境
- 一段內可以串多個相關功能（例：隱私 UID 遮罩 + 移除使用者資料 → 同段「隱私 / 資料清理」）
- 第二人稱直接對讀者：繁中「你的 / 點下去 / 終於不用」；英文 "your / click / no more"
- emoji 偶爾用，每段 1–2 個，挑自然停頓處（句末或破折號前後）；中英文 emoji 位置要對齊
- 過場句 + bullet 區
- 繁中過場：「除此之外，我們還做了：」
- 英文過場："On top of that, we also did:"
- 每條：
主題：細節（可加調皮註解）/Topic: detail (with a cheeky aside if it fits) - 中英文 bullet 條數與順序要一一對應
取得素材
git log <prev-tag>..HEAD --oneline # 看所有 commit
git log <prev-tag>..HEAD --merges --pretty=format:"%h %s" # PR 標題（高層脈絡）
git diff <prev-tag>..HEAD -- README.md README_EN.md # 確認對外講法
git diff <prev-tag>..HEAD --stat | tail -30 # 大致變動規模從 PR 標題挑 2–3 個 hero，其餘進 bullet。Crowdin / Dependabot / 機械 refactor 永遠進 bullet 區或省略。
Gold Standard：v1.1.0（使用者親自校稿後的版本）
## 此版本重點
還記得以前打開歷史記錄表格，滿滿一片只有名字嗎？這次更新後你的「刻晴」終於不只是兩個字——HoYoWiki 整合正式登場，表格、時間軸、分享圖通通長出角色與武器的臉。手癢點下去還有官方立繪、圖庫、描述跟標籤，滑鼠滾輪縮放、雙擊放大、ESC 關掉，一秒切換到 HoYoWiki 看更多，整個分析器瞬間從 Excel 升級成圖鑑 📖
實況主跟截圖黨福音來了：介面 UID 遮罩 🕶️。設定點一下，UID 就只剩前三碼，再也不怕直播時被認親。如果哪天想換電腦重灌，解除安裝程式會貼心問你「要不要連同抽卡記錄、設定、快取一起清掉？」🧹 終於不用自己去翻 AppData 手動刪資料夾了
除此之外，我們還做了：
- 稀有度配色重整：5★ 提亮、新增 1★ 自己的顏色
- 設定頁新增「圖片快取」區塊：看用量、一鍵清圖庫
- 圖片懶載入，不打開詳情就不下載（你的硬碟感謝你）
- 兩輪 Crowdin 翻譯更新：泰 / 越 / 葡（巴） / 烏 / 韓 / 日 / 西 / 法 等
- GitHub Actions Dependabot 上線自動追依賴
- 新增一篇社群介紹文 → 原神資訊站 Genshin Impact Info (https://genshininfo.reh.tw/archives/97)
## What's New
Remember opening the history table and seeing nothing but a wall of names? After this update, your "Keqing" is finally more than two characters of text — HoYoWiki integration is officially here, and your tables, timelines, and share images all grew character and weapon portraits. Click any item and you get the official artwork, gallery, description, and tags; mouse-wheel zoom, double-tap to scale, ESC to close, and a one-click jump to HoYoWiki for more. The analyzer just leveled up from Excel to a full illustrated compendium 📖
Good news for streamers and screenshot folks: UI UID masking 🕶️. One toggle in Settings and your UID is clipped to just the first three digits — no more worrying about being identified mid-stream. And if you ever swap machines or reinstall, the uninstaller now politely asks "want to clear your gacha records, settings, and cache while we're at it?" 🧹 No more digging through AppData by hand.
On top of that, we also did:
- Refreshed rarity colors: brighter 5★ tones, and 1★ finally has its own color
- New "Image Cache" section in Settings: see usage, clear the gallery with one click
- Lazy-loaded gallery: nothing downloads until you open the details (your disk thanks you)
- Two rounds of Crowdin translation updates: Thai / Vietnamese / pt-BR / Ukrainian / Korean / Japanese / Spanish / French, and more
- GitHub Actions Dependabot is now tracking dependencies automatically
- New community write-up → 原神資訊站 Genshin Impact Info (https://genshininfo.reh.tw/archives/97)注意這份範例做對的事：
- 中英文 hero 段落數相同（兩段）、bullet 條數相同（六條）、emoji 位置對齊（📖 / 🕶️ / 🧹）
- 開場 hook：「還記得以前⋯⋯滿滿一片只有名字嗎？」/ "Remember opening the history table⋯"
- 把多個 HoYoWiki 子功能（圖示、詳情、縮放、外連）壓在同一段內
- 把「隱私遮罩」和「解除安裝詢問」綁在同段——情境上相關（資料管理 / 安心感）
- 沒有
## 主打 / ## 體驗 / ## 底層之類分節 - 沒有預設塞「完整 diff」連結或防毒 disclaimer——讓使用者自己決定
- 兩個 H2 直接相鄰，沒有
---分隔線 - 第三方站名「原神資訊站 Genshin Impact Info」用「原文 英譯」雙語並列，中英版本字串相同（不要在英文版只留 "Genshin Info Site"）
重點群組範例
當有多個小功能時，看怎麼把它們合進同一段：
| 主題群 | 包含的功能 |
|---|---|
| 視覺化升級 | HoYoWiki 表格圖示、物品詳情 dialog、圖庫縮放 |
| 隱私 / 資料清理 | UID 遮罩、解除安裝詢問刪資料 |
| 底層變快 | 平行 worker pool、自動補資料 |
| 純功能新增 | 平均出貨抽數統計（通常單獨一段就好） |
Common Mistakes
| ❌ 不要 | ✅ 應該 |
|---|---|
| 只輸出單一語言 | 永遠中英雙語，繁中在上、英文在下，兩個 H2 直接相鄰（不加 ---） |
在中英之間加 --- 水平線 | 兩個 H2 直接相鄰即可 |
| 中英文段落數 / bullet 條數不一致 | 一一對應，emoji 位置也對齊 |
| 英文版把中文站名翻成英譯（如「原神資訊站」→ "Genshin Info Site"）只留英譯 | 第三方站名 / 來源用「原文 英譯」雙語並列，中英版本字串相同（如「原神資訊站 Genshin Impact Info」） |
| 整篇都是 bullet | 主打用散文，次要才 bullet |
### HoYoWiki 整合 / ## 主打功能 分節 | 散文段落自帶轉場，不切標題 |
| 「本次更新包含⋯」「主要新增功能：」開場 | hook 開場（問句、痛點、callback） |
| 列每一條 commit | 只挑使用者會在意的 |
| Emoji 灑滿每行 | 每段 1–2 個，挑自然停頓處 |
| ✨ 主打 / ⚡ 底層 / 🎨 體驗 三段式 | 一段散文走完所有重點 |
| 預設加「完整 diff」連結與防毒 disclaimer | 讓使用者自己決定要不要 |
| 第三人稱客套（「使用者可以⋯」） | 第二人稱直接對讀者（「你⋯」） |
| 把 Crowdin / Dependabot / refactor 拉到 hero | 永遠進 bullet 區 |
| 英文版逐字直譯成生硬中式英文 | 重寫成自然英文，保留同樣的調皮節奏與 hook |
語言與標點
繁中區
- 繁體中文 (台灣)
- 全形標點 ，。！？；：（）「」『』、
- 散文內可用破折號
——作節奏停頓 - 程式碼 / identifier 維持半形
英文區
- 半形標點 . , ! ? ; : ( ) " "
- 散文內可用 em dash
—作節奏停頓（用空格包圍） - 自然口語英文，不要把中文逐字直譯
- 雙引號用直引號
"，不要用花引號""（GitHub markdown 顯示一致性）
草稿流程
git log <prev-tag>..HEAD --merges抓 PR 標題、git log --oneline看細部- 挑 2–3 個 hero（合併相關的），其餘進 bullet
- 先寫繁中版：把「故事」用散文寫清楚，再雕 emoji 和段落節奏
- 再寫英文版：對齊段落結構、bullet 條數、emoji 位置；用自然英文重寫，不逐字直譯
- 兩個 H2 直接相鄰，不要加
--- - 給使用者過稿
- 若使用者改稿後風格有調整 → 回來更新這個技能的 Gold Standard 段落（中英都要更新），下次才不會走回頭路
紅旗自檢
寫完前自問：
- 中英文都寫了？繁中在上、英文在下？兩個 H2 直接相鄰（沒有
---）？ - 中英文段落數、bullet 條數一致？emoji 位置對齊？
- 中文站名 / 來源在英文版有保留「原文 英譯」雙語並列，不是只翻成英文？
- 各語言內是不是只有一個 H2（
## 此版本重點/## What's New）？沒有別的標題？ - 主打功能是不是散文？沒被我寫成 bullet？
- 有沒有第二人稱直接對讀者？
- 是不是不小心又灑了「✨ ⚡ 🎨」三段式分節？
- Crowdin / Dependabot / 機械 refactor 有沒有乖乖待在 bullet 區？
- 英文版讀起來是自然英文，不是中式直譯？
© GoneTone, 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/writing-release-notes of GoneTone/genshin-impact-wish-gacha-analyzer.
Open the folder on GitHubat commit 71ecc39
Compare with similar skills
Writing 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 |
|---|---|---|---|---|---|---|
| Writing Release Notes this skillGoneTone/genshin-impact-wish-gacha-analyzer | 152 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Releasepwrdrvr/openclaw-codex-app-server | 265 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Release Discord Postnevalang/neva | 1.1k | — | ~500 | Automated safety check: Pass | MIT | |
| Subwave Discord Releaseperminder-klair/subwave | 1.4k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Beta Prereleaservdbreemen/OTGW-firmware | 207 | — | ~2.7k | Automated safety check: Pass | GPL-3.0 | |
| Release MaintainerUndertone0809/rudder | 292 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Release Discord Post
nevalang/neva
Create a Discord-ready Neva release announcement from a GitHub release payload.
Subwave Discord Release
perminder-klair/subwave
Draft a Discord release announcement for SUB/WAVE from a release PR, tag, or version number.
Beta Prerelease
rvdbreemen/OTGW-firmware
Publish an OTGW-firmware beta prerelease — bump VERSIONPRERELEASE, push to otgw-1.x.x, tag, and let CI build + publish the GitHub prerelease
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…
Release
LanternOps/breeze
A skill your agent uses when cutting, shipping, or announcing a Breeze RMM release — "cut a release", "ship vX.Y.Z", "release notes for X", "what do self-hosters need to know", "draft the release…
Related
Categories
Questions about Writing Release Notes
What does Writing Release Notes do?
A skill your agent uses when drafting GitHub release notes or changelog content for this project (Genshin Impact Wish Gacha Analyzer). Writing Release Notes is an agent skill from GoneTone/genshin-impact-wish-gacha-analyzer. Use when drafting GitHub release notes or changelog content for this project (Genshin Impact Wish Gacha Analyzer).
When should I use Writing Release Notes?
Writing Release Notes fits situations like: drafting GitHub release notes; changelog content for this project (Genshin Impact Wish Gacha Analyzer); the user asks to write release content for a new version; summarize a tag-to-tag diff (e.g.
How do I install Writing Release Notes in Claude Code?
Run `npx skills add GoneTone/genshin-impact-wish-gacha-analyzer --skill writing-release-notes -a claude-code`. Or copy the skill folder (.claude/skills/writing-release-notes in GoneTone/genshin-impact-wish-gacha-analyzer) into .claude/skills/writing-release-notes in your project. Claude Code loads it when a task matches its description.
How do I install Writing Release Notes in Codex?
Run `npx skills add GoneTone/genshin-impact-wish-gacha-analyzer --skill writing-release-notes -a codex`. Or copy the skill folder (.claude/skills/writing-release-notes in GoneTone/genshin-impact-wish-gacha-analyzer) into .agents/skills/writing-release-notes in your project. Codex loads it when a task matches its description.
Can I use Writing 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 GoneTone/genshin-impact-wish-gacha-analyzer --skill writing-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/writing-release-notes, .gemini/skills/writing-release-notes, .github/skills/writing-release-notes and .opencode/skills/writing-release-notes in your project.
What does Writing Release Notes need to run?
Going by SKILL.md and its folder, Writing Release Notes needs the command-line tools its instructions call (git).
Does Writing Release Notes access the network?
SKILL.md names 1 domain. In commands or code: genshininfo.reh.tw; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Writing 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 Writing Release Notes use?
Writing Release Notes 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 Writing Release Notes use?
About 1.6k tokens (SKILL.md is roughly 6.5k 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 Writing Release Notes?
Skills that share tags, products or a category with Writing Release Notes: Release (pwrdrvr/openclaw-codex-app-server, 265 stars), Release Discord Post (nevalang/neva, 1.1k stars), Subwave Discord Release (perminder-klair/subwave, 1.4k stars) and Beta Prerelease (rvdbreemen/OTGW-firmware, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Writing Release Notes?
GoneTone (a GitHub user) maintains it in GoneTone/genshin-impact-wish-gacha-analyzer, which has 152 GitHub stars. The repository was last updated on October 5, 2026.
Source: GoneTone/genshin-impact-wish-gacha-analyzer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.