Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
Generate and publish formatted GitHub Release Notes for opentiny/genui-sdk.
Install Release Notes
$ npx skills add opentiny/genui-sdk --skill release-notes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install opentiny/genui-sdk 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/opentiny/genui-sdk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/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/opentiny/genui-sdk/tree/dev/.agents/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/opentiny/genui-sdk/tree/dev/.agents/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 opentiny/genui-sdk --skill release-notes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install opentiny/genui-sdk release-notes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opentiny/genui-sdk.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/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/opentiny/genui-sdk/tree/dev/.agents/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 opentiny/genui-sdk --skill release-notes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install opentiny/genui-sdk release-notes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opentiny/genui-sdk.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/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/opentiny/genui-sdk/tree/dev/.agents/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/opentiny/genui-sdk.git --path .agents/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 opentiny/genui-sdk --skill release-notes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install opentiny/genui-sdk release-notes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opentiny/genui-sdk.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/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/opentiny/genui-sdk/tree/dev/.agents/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 opentiny/genui-sdk 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 opentiny/genui-sdk --skill release-notes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/opentiny/genui-sdk.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/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/opentiny/genui-sdk/tree/dev/.agents/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 opentiny/genui-sdk --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 opentiny/genui-sdk release-notes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/opentiny/genui-sdk.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/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/opentiny/genui-sdk/tree/dev/.agents/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
- 171
- Token cost
- ~1.4k tokens
- SKILL.md length
- 317 words
- Files
- 3 (incl. scripts)
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Generate and publish formatted GitHub Release Notes for opentiny/genui-sdk.
- Works in 6 steps: ：确定版本 → ：拉取 PR 数据 → ：语法修复与润色 → …
- The user asks to create release notes
- SKILL.md covers 前置检查, 工作流 and 常见问题
- Runs Shell scripts from its folder; calls git and gh; needs GH_TOKEN
What it does
Release Notes is an agent skill from opentiny/genui-sdk. Generate and publish formatted GitHub Release Notes for opentiny/genui-sdk. Compares the new tag with the previous stable release, fetches PRs, polishes titles, formats notes by area and change type, and writes the result to releaseNote.md at the repo root. Use when the user asks to create release notes, publish a release, or prepare a changelog for genui-sdk.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts (for example `examples.md` and `scripts/fetch-release-data.sh`).
It sits in Development, covering Changelog and release notes. It works with GitHub. The repository describes itself as: A Generative UI SDK for Vue, Angular and React. The licence is MIT.
When your agent uses it
- The user asks to create release notes
- Publish a release
- Prepare a changelog for genui-sdk
Example prompts
- “/release-notes”
Requirements
- A Bash shell
Workflow steps
6 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 69578e3. 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:
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 these keys or tokens, usually read from environment variables:
GH_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Release Notes loads about 1.4k tokens when it runs. Until then it costs about 94 tokens; SKILL.md has 317 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 opentiny/genui-sdk at commit 69578e3, republished under its MIT licence (© opentiny). 317 words, ~1,435 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
- Generate and publish formatted GitHub Release Notes for opentiny/genui-sdk. Compares the new tag with the previous stable release, fetches PRs, polishes titles, formats notes by area and change type, and writes the result to releaseNote.md at the repo root. Use when the user asks to create release notes, publish a release, or prepare a changelog for genui-sdk.
Genui SDK Release Notes
为 opentiny/genui-sdk 生成并发布 Release Notes。
前置检查
执行前确认：
- GitHub CLI：
gh auth status已通过。若未安装或未登录，用 AskQuestion 询问用户：- 是否安装并登录
gh（推荐，可自动拉取 PR 与发布） - 或手动提供：新 tag、上一正式版 tag、GitHub 自动生成的 Release notes 原文
- 是否安装并登录
- Tag 信息：明确本次发布的 tag（如
v1.3.0） - 上一正式版：不含
alpha/beta的最近 tag（如v1.2.0）。用git tag --sort=-v:refname筛选
正式版判定：匹配 ^v\d+\.\d+\.\d+$，排除 alpha/beta 预发布工作流
进度：
- [ ] 1. 确定 new_tag 与 previous_tag
- [ ] 2. 拉取 PR 列表与原始 Release notes
- [ ] 3. 修复 PR 标题的语法错误并进行适当润色
- [ ] 4. 提炼 Highlights、按规则分类并格式化
- [ ] 5. 写入 releaseNote.md 并请用户确认
- [ ] 6. 发布 ReleaseStep 1：确定版本
git fetch --tags
git tag --merged <new_tag> --sort=-v:refname \
| grep -E '^v[0-9]+\.[0-9]+\.[0-9]+$' \
| grep -vx '<new_tag>'new_tag：用户指定或最新待发布 tagprevious_tag：上述列表第一条（已合入 new_tag、且排除自身的最近正式版）
Step 2：拉取 PR 数据
优先用本 skill 目录下的脚本：
scripts/fetch-release-data.sh <new_tag> <previous_tag>脚本输出 JSON，包含 new_tag、previous_tag、full_changelog_url、new_contributors、github_notes，以及 pull_requests 数组，其中每个 PR 含 number、title、author、url、files、commits。
若无 gh，备选方案：
git log <previous_tag>..<new_tag> --pretty=format:'%s%n%b'或请用户从 新建 Release 页 选择 tag、对比 previous_tag 后，将 GitHub 自动生成的 notes 粘贴到对话中。
也可用 GitHub API（需 GH_TOKEN）：
gh api repos/opentiny/genui-sdk/releases/generate-notes \
-f tag_name='<new_tag>' -f previous_tag_name='<previous_tag>' \
-f configuration_file_path='.github/release.yml' 2>/dev/null || trueStep 3：语法修复与润色
对每条 PR 标题做英文语法纠正，规则：
- 保持 conventional commit 前缀与 scope 不变（如
feat(playground):、fix(core):） - 只修正语法、大小写、措辞，不改变技术含义
- 同一 PR 多条 commit 时，分别润色每条描述
Step 4：分类与格式化
Highlights 摘要
在标题之后、Features 之前撰写 3–7 条 Highlights，提炼本版本的主线变更：
- 每条以 粗体主题 起头，简述变更与影响，末尾用括号附主要 PR 编号
- 将关联 PR 归并为一组（如「多框架渲染」「生命周期增强」），不要逐条罗列所有 PR
- 仅收录有用户可见影响或架构意义的变更；纯 chore / ci 不进 Highlights
- 格式：
- **{主题}** - {描述} (#xxx, #yyy).
变更类型（第一级）
| 前缀 / 类型 | 章节 |
|---|---|
feat | ✨ Features |
fix | 🐛 Bug Fixes |
refactor | ♻️ Refactor |
docs、ci、build、test、纯测试描述 | 🔧 Other Changes |
例外（不论前缀，归入 Other Changes 对应子区）：
sites/homepage或 scope 含homepage→ Sitepackages/benchmarks或标题含benchmarks→ Benchmarksdocs/或docs:→ Docs.github/、ci:、build(→ Build- 测试相关 → Test
区域（第二级子标题）
按 PR 改动路径与标题 scope 判定，优先级从高到低：
| 子区 | 判定条件 |
|---|---|
| Benchmarks | packages/benchmarks |
| Site | sites/homepage、(homepage) |
| Docs | docs/、docs: |
| Build | .github/、ci:、build( |
| Test | 测试文件或标题为测试用例补充 |
| Playground | sites/playground、(playground)、genui-template、template（非 homepage） |
| Components | packages/、projects/ 中其余改动 |
条目格式
- {润色后的标题} by @{author} in https://github.com/opentiny/genui-sdk/pull/{number}同一 PR 有多条独立 commit 需分别列出时，末尾追加 commit hash：
- {标题} by @{author} in https://github.com/opentiny/genui-sdk/pull/{number} - {full_sha}注意：in 与 URL 之间保留空格；有 hash 时用 - 分隔。
文档结构
# Genui SDK v{version} Release Notes
## 🚀 Highlights
- **{主题}** - {描述} (#xxx, #yyy).
- ...
---
## ✨ Features
**Components**
- ...
**Playground**
- ...
---
## 🐛 Bug Fixes
**Components**
- ...
---
## ♻️ Refactor
...
---
## 🔧 Other Changes
**Test**
- ...
**Build**
- ...
**Docs**
- ...
**Site**
- ...
**Benchmarks**
- ...
---
## 🎉 New Contributors
- @{login} made their first contribution in https://github.com/opentiny/genui-sdk/pull/{number}
**Full Changelog**: https://github.com/opentiny/genui-sdk/compare/{previous_tag}...{new_tag}规则：
- 标题保留
v前缀（如Genui SDK v1.2.0 Release Notes） - 子区按固定顺序：Components → Playground → Test → Build → Docs → Site → Benchmarks
- 空子区省略；空章节省略
- 大章节之间用
---分隔 - Highlights：标题后、Features 前放 3–7 条主线变更；每条以 粗体主题 起头，简述影响并附主要 PR 编号；仅收录有用户可见影响或架构意义的变更，纯 chore / ci 不进 Highlights
- New Contributors：取自脚本输出的
new_contributors（字段为login、number），格式为- @{login} made their first contribution in https://github.com/opentiny/genui-sdk/pull/{number}；无首次贡献者则省略整个章节 - Full Changelog：固定取脚本输出的
full_changelog_url，置于文档最末
完整示例见 examples.md。
Step 5：写入文件并确认
将格式化后的 Release Notes 写入仓库根目录 releaseNote.md（覆盖已有内容），并在对话中展示全文请用户确认。
# 输出路径（固定）
releaseNote.md规则：
- 每次整理完成后必须写入
releaseNote.md，不要只输出到对话或/tmp - 用户反馈调整后，同步更新
releaseNote.md - 确认无误后再进入发布步骤
Step 6：发布
CLI 发布（推荐）：
git push origin <new_tag>
gh release create <new_tag> \
--verify-tag \
--title "Genui SDK <new_tag>" \
--notes-file releaseNote.md \
--repo opentiny/genui-sdk预发布版本加 --prerelease。
网页发布：用户确认后，引导打开 releases/new，选择 tag、粘贴 releaseNote.md 内容、点击 Publish。
常见问题
| 情况 | 处理 |
|---|---|
gh 未安装 | 询问用户安装，或用手动粘贴 GitHub 生成的 notes；整理结果仍写入 releaseNote.md |
无 .github/release.yml | 直接用 fetch-release-data.sh 或 git log 从提交信息提取 PR 编号 |
| 同一 PR 跨多个区域 | 按主要改动区域归类；多 commit 可拆成多条 |
| dependabot 等机器人 PR | 归入 Other Changes > Build，或按用户要求忽略 |
releaseNote.md 已存在 | 直接覆盖为本次整理结果 |
© opentiny, 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/release-notes of opentiny/genui-sdk.
- SKILL.md
- examples.md
- scripts/fetch-release-data.sh
Open the folder on GitHubat commit 69578e3
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 skillopentiny/genui-sdk | 171 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Mole CLI Release Flowtw93/Mole | 70k | — | ~2.5k | Automated safety check: Pass | GPL-3.0 | |
| Draft Release Notesjamiepine/voicebox | 57k | — | ~941 | Automated safety check: Pass | MIT | |
| Mole Release Notes Publishertw93/Mole | 70k | — | ~1.9k | Automated safety check: Pass | GPL-3.0 | |
| Release Bumpjamiepine/voicebox | 57k | — | ~1.1k | Automated safety check: Pass | MIT |
Similar skills
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.
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.
Mole Release Notes Publisher
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.
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.
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.
More from opentiny/genui-sdk
Genui Integration
opentiny/genui-sdk
genui-sdk 全方位指南：安装、配置、集成、示例。用户提到 genui-sdk、genui-sdk-server，或想构建 AI 聊天界面、动态 UI 组件、Node.js 后端 LLM 代理（OpenAI 兼容 chat/completions API）时使用。涵盖 Vue/Angular 前端（主题、物料、GenuiChat/GenuiRenderer）与 Server…
Docs I18n
opentiny/genui-sdk
Sync GenUI SDK docs between Chinese and English when adding, editing, renaming, or deleting documentation under docs/.
Publicity Article
opentiny/genui-sdk
Write GenUI SDK version publicity articles for 掘金, 公众号, and other platforms from release notes.
Update Docs PR
opentiny/genui-sdk
After publishing a new @opentiny/genui-sdk package, update opentiny/docs (submodule, genui package versions, VitePress sidebar) and opentiny/opentiny.design (submodule commit only), then open PRs on…
Related
Works with
Categories
Questions about Release Notes
What does Release Notes do?
Generate and publish formatted GitHub Release Notes for opentiny/genui-sdk. Release Notes is an agent skill from opentiny/genui-sdk. Generate and publish formatted GitHub Release Notes for opentiny/genui-sdk.
When should I use Release Notes?
Release Notes fits situations like: the user asks to create release notes; publish a release; prepare a changelog for genui-sdk.
How do I install Release Notes in Claude Code?
Run `npx skills add opentiny/genui-sdk --skill release-notes -a claude-code`. Or copy the skill folder (.agents/skills/release-notes in opentiny/genui-sdk) 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 opentiny/genui-sdk --skill release-notes -a codex`. Or copy the skill folder (.agents/skills/release-notes in opentiny/genui-sdk) 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 opentiny/genui-sdk --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 a shell for the scripts in its folder, the command-line tools its instructions call (git and gh) and credentials named GH_TOKEN. Our summary lists: A Bash shell.
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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Release Notes use?
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 Release Notes use?
About 1.4k tokens (SKILL.md is roughly 5.7k 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: Cutting A Release (TriliumNext/Trilium, 38k stars), Mole CLI Release Flow (tw93/Mole, 70k stars), Draft Release Notes (jamiepine/voicebox, 57k stars) and Mole Release Notes Publisher (tw93/Mole, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Release Notes?
opentiny (a GitHub organization) maintains it in opentiny/genui-sdk, which has 171 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.
Source: opentiny/genui-sdk on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.