Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add laolaoshiren/claude-code-skills-zh --skill changelog-gengit clone --depth 1 https://github.com/laolaoshiren/claude-code-skills-zhWrote 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/laolaoshiren/claude-code-skills-zh/changelog-gen)<a href="https://agentmods.dev/skills/laolaoshiren/claude-code-skills-zh/changelog-gen"><img src="https://agentmods.dev/badge/skills/laolaoshiren/claude-code-skills-zh/changelog-gen/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/laolaoshiren/claude-code-skills-zh/changelog-gen"><img src="https://agentmods.dev/badge/skills/laolaoshiren/claude-code-skills-zh/changelog-gen.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00019 | $0.00908 |
| Opus 5.5 | $0.00008 | $0.00363 |
| Sonnet 5.5 | $0.00004 | $0.00182 |
| Haiku 4.5 | $0.00002 | $0.00091 |
Grade A, and why
changelog-gen 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 1mo 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.
What it actually says
Changelog 自动生成
触发条件
当用户要求生成 changelog、更新日志、版本记录、release notes 时激活此技能。
工作流程
第 1 步：获取 Git 历史
# 先获取最近的 tag，再用 revision range 查询
git describe --tags --abbrev=0
git log --oneline <last-tag>..HEAD
# 或指定范围
git log --oneline v1.0.0..HEAD
# 仓库没有 tag 时，明确选择起始提交或查看全部历史
git log --oneline
第 2 步：分类提交
按 Conventional Commits 分类：
| 分类 | Type 标识 | 图标 |
|---|---|---|
| 新功能 | feat |
✨ |
| Bug 修复 | fix |
🐛 |
| 文档 | docs |
📝 |
| 重构 | refactor |
♻️ |
| 性能优化 | perf |
⚡ |
| 测试 | test |
🧪 |
| 构建/工具 | chore |
🔧 |
| Breaking Changes | 含 BREAKING CHANGE: 或 ! |
⚠️ |
| 安全修复 | fix(security) 或含 CVE |
🔒 |
| 依赖更新 | deps 或 chore(deps) |
📦 |
第 3 步：版本号确定策略
遵循 Semantic Versioning 规则：
| 变更类型 | 版本变化 | 示例 |
|---|---|---|
| Breaking Changes | 主版本 +1 | 1.2.0 → 2.0.0 |
| 新功能 (feat) | 次版本 +1 | 1.2.0 → 1.3.0 |
| Bug 修复 (fix) | 修订版本 +1 | 1.2.0 → 1.2.1 |
| 安全修复 (fix(security)) | 修订版本 +1（紧急发布） | 1.2.0 → 1.2.1 |
判断依据：
- 提交信息含
BREAKING CHANGE:或 type 后加!（如feat!:）→ 主版本 - 存在
feat提交 → 次版本 - 仅
fix/docs/chore等 → 修订版本
第 4 步：生成 CHANGELOG
输出格式
# Changelog
## [1.3.0] - 2026-06-17
### ⚠️ Breaking Changes
- 移除废弃的 `/api/v1/users` 端点，统一使用 `/api/v2/users` (#130)
### ✨ 新功能
- 新增用户认证模块 (#123)
- 支持 OAuth2 登录 (#124)
- 新增批量导出功能 (#128)
### 🔒 安全修复
- 升级 lodash 修复原型污染漏洞 CVE-2025-XXXX (#129)
### 🐛 Bug 修复
- 修复分页查询偏移量错误 (#125)
- 修复并发写入导致的数据竞争 (#127)
### ⚡ 性能优化
- 优化大列表渲染性能，减少 50% 内存占用 (#126)
### 📝 文档
- 更新 API 文档 (#131)
### 📦 依赖更新
- 升级 axios 1.6.0 → 1.7.0 (#132)
注意事项
- Breaking Changes 必须放在最前面，加粗突出显示
- 每条记录关联 Issue/PR 编号，便于追溯
- 安全修复需注明 CVE 编号（如有）
- 版本号应与 git tag 保持一致
- 如果是预发布版本，使用
-beta.1、-rc.1后缀 - 可维护一个
CHANGELOG.md文件，每次 release 追加到顶部
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.
- 1mo ago First seen · 99 lines · 19 tokens per session scan A 456e7da97e27
changelog-gen is a skill published in the GitHub repository laolaoshiren/claude-code-skills-zh (900 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 908 once invoked, about $0.0001 per session on Opus 5.5. 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-30.
Other skills, from other repositories
antigravity-maintainer-batch-release
Run protected AAS maintainer sweeps, PR merge batches, canonical sync, Core preview checks, and scripted releases. Use for repository maintenance, main alignment, CLI/MCP/Workbench changes, or release work; not ordinary contribution tasks.
dev-ship
Fechamento de feature — verificação goal-backward antes de declarar pronto. Roda Must-Haves do PLAN.md, executa o demo script, revisa o diff completo procurando bugs e restos (debug logs, TODOs, código morto), passa lente de segurança nos arquivos tocados, escreve SUMMARY.md e arquiva o plano. Use quando o usuário…
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
changelog-from-commits
Generate a user-facing CHANGELOG entry from raw git log output. Use when the user is preparing a release, says "what changed since last version", asks to write release notes, or wants to summarize a batch of commits for end users.
release-skills
A release workflow for preparing and publishing a new version of a software project. A release is a named version that may include updated version files, release notes, tags, or a GitHub Release.
git-workflow
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.