Borrowing it
Nothing to install: this file belongs to CavinHuang/lume. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/CavinHuang/lume/main/.claude/skills/release-notes/SKILL.mdgit clone --depth 1 https://github.com/CavinHuang/lumeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/cavinhuang/lume/release-notes)<a href="https://agentmods.dev/skills/cavinhuang/lume/release-notes"><img src="https://agentmods.dev/badge/skills/cavinhuang/lume/release-notes/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cavinhuang/lume/release-notes"><img src="https://agentmods.dev/badge/skills/cavinhuang/lume/release-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01806 |
| Opus 5.5 | $0.00000 | $0.00722 |
| Sonnet 5.5 | $0.00000 | $0.00361 |
| Haiku 4.5 | $0.00000 | $0.00181 |
Grade A, and why
release-notes scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes Generator
生成用户可读的版本发布说明，CI 直接读取发布。
Core Principle
Release notes are not a formatted changelog. They explain to users what changed and why it matters to them — written as if the team is walking them through the update.
commit 原始信息 → 用户视角翻译 → 发布说明
禁止： 将 raw commits 直接填入发布说明（如 feat(ci): read release notes from file）。每条都必须翻译为用户能理解的语言。
Flow
确定版本 → 读取 commit → 分类 + 用户价值翻译 → 生成 Markdown → 写入 docs/release/vX.Y.Z.md → 预览确认
Step 1: 确定版本
git describe --tags --abbrev=0 # 上一个 tag
cat package.json | grep '"version"' # 当前版本
- 用户指定版本号（如
v0.2.0）→ 直接使用 - 用户说 "patch/minor/major" → 按 semver 递增
- 不确定 → 问用户
Step 2: 读取 Commit 历史
git log <lastTag>..HEAD --oneline # 有 tag 时
git log --oneline # 无 tag 时
Step 3: 分类 + 用户价值翻译
分类
| 分类 | emoji | 前缀 | 是否面向用户 |
|---|---|---|---|
| Features | 🚀 | feat |
✅ 是 |
| Bug Fixes | 🐛 | fix |
✅ 是 |
| Breaking Changes | ⚠️ | BREAKING: |
✅ 是（独立 section） |
| Refactoring | ♻️ | refactor |
❌ 内部 |
| Documentation | 📝 | docs |
❌ 内部 |
| Maintenance | 🔧 | chore |
❌ 内部 |
| Performance | ⚡ | perf |
✅ 是（如用户感知加速） |
未匹配 → 🔔 Other
用户价值翻译（关键）
每条面向用户的 commit 翻译为 用户能理解的语言：
| 原始 commit | 用户视角翻译 |
|---|---|
feat(ci): read release notes from file |
发布流程改进 — 发布说明现在自动生成 |
fix(desktop): tauri.conf.json pubkey |
修复桌面端自动更新签名验证 |
chore: release script main flow |
新的版本发布脚本，支持自动 bump + tag + push |
规则：
- 保留 scope 括号，补充一句中文解释变更范围
- 内部实现细节（如 "extract function", "use readFileSync"）→ 一句话概括目的，不列技术点
- 同类合并 — 同一 scope 下 3+ 相似 commit → 合并为一条，注明数量
- scope 信息必须保留，便于读者理解变更范围
破坏性变更（BREAKING）
- 提取
BREAKING:前缀的 commit → 放入 独立 section## ⚠️ Breaking Changes - 说明影响范围 + 迁移建议
- 放在 Highlights 之后，Features 之前
语言处理
commit message 可能混合中英文：
- 面向用户的部分 → 统一为 中文说明
- 保留技术术语原文（如
tauri-action,bun,N-API）
Step 4: 生成发布说明
文件路径
docs/release/vX.Y.Z.md # 必须有 v 前缀 — CI 读取 github.ref_name (如 v0.2.0)
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2mo ago First seen · 216 lines · 0 tokens per session scan A 977aff0e640d
release-notes is a skill published in the GitHub repository CavinHuang/lume (3 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,806 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
github-ops
GitHub CLI for issues, PRs, code search, CI logs, releases, and API queries. Requires gh CLI and auth.
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
git-story-film
Direct an animated film of about two minutes from a software repository's Git history. Select real commits, releases and reverts; develop the story, character and visual style; build an outline, cast sheet, storyboard and HTML review studio; then render a 4K/60fps MP4 after approval. Use for repository or product…
omh-release-cut
This is an OMH release-cut workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).