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.
git clone --depth 1 https://github.com/Mr-chen-05/rules-2.1-optimizedWrote 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/rules/mr-chen-05/rules-2.1-optimized/changelog-management)<a href="https://agentmods.dev/rules/mr-chen-05/rules-2.1-optimized/changelog-management"><img src="https://agentmods.dev/badge/rules/mr-chen-05/rules-2.1-optimized/changelog-management.svg" alt="Measured on agentmods" 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.05802 | $0.05802 |
| Opus 5 | $0.02901 | $0.02901 |
| Sonnet 5 | $0.01160 | $0.01160 |
| Haiku 4.5 | $0.00580 | $0.00580 |
Grade A, and why
changelog-management 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 7d 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 — 798 lines — stays where its author put it; the contents beside it link to each section on GitHub.
📋 Changelog Management - 智能变更日志管理
AI驱动的自动化变更日志生成和管理系统，集成版本控制、智能分类和格式化输出。
🧠 AI Intelligence Core - AI智能核心
智能激活条件
自动激活场景:
- 检测到版本标签创建或更新
- 用户执行 "/changelog" 相关命令
- 项目进入发布准备阶段
- 超级大脑系统推荐生成变更日志
- 集成到commit工作流中（支持 /commit-fast 别名）
智能分析维度:
- 提交历史分析和分类 (35%)
- 版本语义化识别 (25%)
- 变更影响评估 (20%)
- 用户关注度分析 (15%)
- 发布时机判断 (5%)
🚀 Commands - 智能命令
/changelog- 生成完整变更日志/changelog --since <version>- 生成指定版本以来的变更/changelog --auto- 自动化生成并更新文件/changelog --preview- 预览变更日志内容/changelog --format <type>- 指定输出格式 (markdown/json/html)/changelog --release- 生成发布版本变更日志
✨ AI-Powered Features - AI驱动功能
🤖 智能提交分析引擎
提交历史挖掘:
语义分析:
- 自动解析约定式提交格式
- 识别提交类型和作用域
- 提取关键变更信息
- 分析变更重要性和影响
智能分类:
- 功能增强 (Features)
- 问题修复 (Bug Fixes)
- 性能改进 (Performance)
- 安全更新 (Security)
- 文档更新 (Documentation)
- 开发工具 (Development)
- 重大变更 (Breaking Changes)
影响评估:
- 用户可见性评估
- API兼容性分析
- 性能影响评估
- 安全影响分析
🔧 版本管理集成
版本识别:
语义化版本:
- 自动识别 MAJOR.MINOR.PATCH 格式
- 支持预发布版本 (alpha, beta, rc)
- 处理版本标签和分支
- 智能版本号建议
发布管理:
- 自动检测发布候选
- 生成发布说明
- 集成CI/CD流水线
- 支持多环境发布
历史追踪:
- 维护完整版本历史
- 跟踪版本间差异
- 生成版本对比报告
- 支持版本回滚信息
📝 智能内容生成
内容生成引擎:
自动摘要:
- 生成版本亮点摘要
- 提取关键功能描述
- 创建用户友好的说明
- 生成技术细节补充
格式化输出:
- Markdown格式 (默认)
- JSON结构化数据
- HTML网页格式
- 纯文本格式
多语言支持:
- 中英文双语生成
- 技术术语标准化
- 用户友好的表达
- 开发者详细信息
📋 Changelog Structure - 变更日志结构
🎯 标准格式模板
文档结构:
头部信息:
- 项目名称和描述
- 版本管理说明
- 最后更新时间
- 生成工具信息
版本条目:
- 版本号和发布日期
- 版本类型 (Major/Minor/Patch)
- 变更摘要
- 详细变更列表
分类组织:
- 🚀 新功能 (Added)
- 🔧 功能改进 (Changed)
- 🗑️ 废弃功能 (Deprecated)
- 🔥 移除功能 (Removed)
- 🐛 问题修复 (Fixed)
- 🔒 安全更新 (Security)
📄 生成模板示例
# 📋 变更日志
本项目的所有重要变更都将记录在此文件中。
格式基于 [Keep a Changelog](https://keepachangelog.com/zh-CN/1.0.0/)，
版本号遵循 [语义化版本](https://semver.org/lang/zh-CN/)。
## [未发布]
### 🚀 新增
- 新功能描述
### 🔧 变更
- 功能改进描述
### 🐛 修复
- 问题修复描述
### 🚀 新增
- ✨ 添加AI驱动的快速提交工作流
- 🧠 集成超级大脑系统智能推荐
- 🔧 实现MCP工具自动编排
### 🔧 变更
- ♻️ 重构提交信息生成逻辑
- ⚡️ 优化文件暂存性能
- 🎨 改进用户界面体验
### 🐛 修复
- 🐛 修复大文件处理超时问题
- 🔧 解决并发提交冲突
- 📝 修正文档格式错误
### 🔒 安全
- 🔒 加强敏感信息检测
- 🛡️ 改进权限验证机制
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.
- 7d ago First seen · 798 lines · 5,802 tokens per session scan A 166f307ea63f
changelog-management is a cursor rule published in the GitHub repository Mr-chen-05/rules-2.1-optimized (172 stars, last pushed 10mo ago), licensed MIT. It adds 5,802 tokens to every session, about $0.0290 per session on Opus 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 cursor rules, from other repositories
monorepo-versioning
Internal peerDependency ranges and Changesets conventions for the SDK monorepo — avoid major-version cascades.
release-notes
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
release-checklist
What to update with each code change or version release.
release-policy
Release, versioning, and signing policy for setmac.
bump-project-version
The user can provide version in one of three ways.