Borrowing it
Nothing to install: this file belongs to u9401066/rootcause-mcp. 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/u9401066/rootcause-mcp/master/.claude/skills/changelog-updater/SKILL.mdgit clone --depth 1 https://github.com/u9401066/rootcause-mcpWrote 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/u9401066/rootcause-mcp/changelog-updater)<a href="https://agentmods.dev/skills/u9401066/rootcause-mcp/changelog-updater"><img src="https://agentmods.dev/badge/skills/u9401066/rootcause-mcp/changelog-updater/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/u9401066/rootcause-mcp/changelog-updater"><img src="https://agentmods.dev/badge/skills/u9401066/rootcause-mcp/changelog-updater.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.01512 |
| Opus 5 | $0.00000 | $0.00756 |
| Sonnet 5 | $0.00000 | $0.00302 |
| Haiku 4.5 | $0.00000 | $0.00151 |
Grade A, and why
changelog-updater 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 10d 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.
This is a copy
100% identical to changelog-updater — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CHANGELOG 更新技能
描述
根據變更內容自動更新 CHANGELOG.md，遵循 Keep a Changelog 格式。
觸發條件
- 「更新 changelog」「CL」「變更紀錄」
- 被
git-precommit編排器調用 - 功能完成後需要記錄時
法規依據
- 憲法：CONSTITUTION.md 第 7 條
- 格式：Keep a Changelog 1.1.0
📁 CHANGELOG.md 標準格式
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/),
and this project adheres to [Semantic Versioning](https://semver.org/).
## [Unreleased]
### Added
- 待發布的新功能
## [1.2.0] - 2026-01-15
### Added
- 新增用戶認證模組 (#123)
- 新增密碼重設功能
### Changed
- 改進登入頁面 UI
### Fixed
- 修復登出後 session 未清除問題 (#456)
## [1.1.0] - 2026-01-01
### Added
- 初始版本功能
🔧 操作步驟
Step 1: 讀取現有 CHANGELOG
read_file("CHANGELOG.md")
Step 2: 取得變更資訊
從 git-precommit 調用時，分析變更內容：
get_changed_files()
或從使用者提供的變更描述判斷。
Step 3: 分類變更
| 類型 | 使用時機 | 關鍵字偵測 |
|---|---|---|
| Added | 新功能 | 新增, add, feat, create |
| Changed | 修改現有功能 | 變更, 修改, update, change, refactor |
| Deprecated | 即將移除的功能 | 棄用, deprecate |
| Removed | 已移除的功能 | 移除, 刪除, remove, delete |
| Fixed | Bug 修復 | 修復, fix, bug, resolve |
| Security | 安全性修復 | 安全, security, 漏洞, CVE |
Step 4: 判斷版本號
MAJOR.MINOR.PATCH
├── MAJOR: 不相容的 API 變更（Breaking Changes）
│ - 移除功能
│ - API 簽名變更
│ - 資料格式變更
│
├── MINOR: 新增功能（向下相容）
│ - 新增 API
│ - 新增功能模組
│ - 新增設定選項
│
└── PATCH: Bug 修復（向下相容）
- 修復錯誤
- 安全性修補
- 文檔修正
Step 5: 更新 CHANGELOG
方式 A：新增到 Unreleased（推薦用於開發中）
oldString: "## [Unreleased]\n\n### Added"
newString: "## [Unreleased]\n\n### Added\n- 新增功能描述"
方式 B：發布新版本（用於 release）
oldString: "## [Unreleased]\n\n### Added\n- 新功能"
newString: "## [Unreleased]\n\n## [1.2.0] - 2026-01-15\n\n### Added\n- 新功能"
📝 條目撰寫規範
好的寫法
### Added
- 新增使用者認證模組，支援 OAuth2.0 (#123)
- 實作密碼強度檢查功能
### Fixed
- 修復登出後 session 未正確清除的問題 (#456)
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.
- 10d ago First seen · 218 lines · 0 tokens per session scan A 7e17b2a47f95
changelog-updater is a skill published in the GitHub repository u9401066/rootcause-mcp (0 stars, last pushed 8d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,512 tokens. A static security scan graded it A with 0 findings. It is 100% identical to changelog-updater, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
changelog-updater
A workflow for updating CHANGELOG.md, the file that records what changed between software releases, using the Keep a Changelog format. It classifies changes such as new features, fixes, removals, and security updates.
git-doc-updater
A Git workflow that checks whether key project documentation still matches the code before a commit, push, or release.
han-release
Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…
release-expert
Multi-repo release coordination: version alignment, RC lifecycle, release waves, rollback planning. Use when saying "release", "version alignment", or "cut an RC".
release
Guide through the Cortex TMS release process — version bump, changelog, sync, tag, publish. Every step requires user approval.
changelog
Record shipped work in the monthly changelog (append-only). Use when something ships or when asked "what changed", "add to changelog", "release notes", or "what shipped this month".