Borrowing it
Nothing to install: this file belongs to Asheng008/unifiles-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/Asheng008/unifiles-mcp/main/.cursor/commands/update-changelog.mdgit clone --depth 1 https://github.com/Asheng008/unifiles-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/commands/asheng008/unifiles-mcp/update-changelog)<a href="https://agentmods.dev/commands/asheng008/unifiles-mcp/update-changelog"><img src="https://agentmods.dev/badge/commands/asheng008/unifiles-mcp/update-changelog/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/commands/asheng008/unifiles-mcp/update-changelog"><img src="https://agentmods.dev/badge/commands/asheng008/unifiles-mcp/update-changelog.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.01295 |
| Opus 5 | $0.00000 | $0.00647 |
| Sonnet 5 | $0.00000 | $0.00259 |
| Haiku 4.5 | $0.00000 | $0.00129 |
Grade A, and why
update-changelog 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
更新 CHANGELOG.md 文档
根据当前对话中的变更,更新 CHANGELOG.md 文件,记录版本变更。
目标
- 更新
CHANGELOG.md文件,记录当前版本的变更 - 遵循 Keep a Changelog 格式
- 使用 Semantic Versioning 版本号
- 将变更归类到合适的类别(Added, Changed, Deprecated, Removed, Fixed, Security)
必做步骤
-
若 CHANGELOG.md 不存在则创建
- 若项目根目录下不存在
CHANGELOG.md,则先创建该文件 - 写入标准格式:标题、说明、
[Unreleased]部分(位于最前面,所有版本之前) - 创建完成后,再执行下面的步骤
- 若项目根目录下不存在
-
读取当前 CHANGELOG.md 和版本信息
- 读取
CHANGELOG.md查看现有格式和最新版本 - 读取
pyproject.toml获取当前版本号(version字段) - 读取
src/unifiles_mcp/__init__.py确认版本号(如有)
- 读取
-
分析当前对话的变更
- 回顾整个对话历史,识别所有变更:
- Added: 新增功能、工具、文件
- Changed: 修改现有功能、API 变更、重构
- Deprecated: 标记为废弃的功能
- Removed: 删除的功能、文件
- Fixed: Bug 修复
- Security: 安全相关改进
- 按类别组织变更项
- 回顾整个对话历史,识别所有变更:
-
确定版本号
- 如果当前版本在 CHANGELOG 中已存在,更新该版本条目
- 如果当前版本不存在,创建新版本条目
- 版本号格式:
## [版本号] - YYYY-MM-DD - 日期使用当前日期(格式:YYYY-MM-DD)
-
更新 CHANGELOG
- 如果当前版本已存在,在该版本下添加/更新变更项
- 如果当前版本不存在:
- 在
[Unreleased]之后插入新版本条目([Unreleased]应位于所有版本之前) - 保持
[Unreleased]在最前面(标题和说明之后,所有版本之前)
- 在
- 每个变更项使用列表项(
-),按模块或功能分组 - 变更描述要清晰、具体,说明做了什么
-
更新 [Unreleased] 部分(如需要)
- 如果对话中有计划但未实现的功能,更新
[Unreleased]的Planned部分 - 移除已实现的功能
- 如果对话中有计划但未实现的功能,更新
格式要求
- 版本标题:
## [版本号] - YYYY-MM-DD - 分类标题:
### Added,### Changed,### Fixed等(三级标题) - 变更项: 使用列表项
-,可以嵌套子项(用 2 个空格缩进) - 工具描述: 按模块分组(Excel 工具、PDF 工具、Word 工具、SQLite 工具、基础设施等)
- 变更描述: 简洁明了,说明具体做了什么
变更分类指南
- Added: 新增功能、新工具、新文件、新依赖
- Changed: API 变更、参数格式变更、重构、配置变更
- Removed: 删除的功能、删除的文件、移除的依赖
- Fixed: Bug 修复、错误处理改进
- Security: 安全加固、漏洞修复、权限控制
示例格式
## [0.1.2] - 2026-02-07
### Changed
- 工具参数改为平铺参数,不再使用 Pydantic BaseModel
- 所有工具使用 `Annotated[T, Field(description=...)]` 定义参数
- 校验在函数内部通过 `validators` 完成
### Removed
- 删除 `config.py` 配置模块
- 服务器名称改为硬编码 `"unifiles-mcp"`
- 移除路径白名单功能(`allowed_paths`)
### Fixed
- 修复参数顺序错误:无默认值参数必须位于有默认值参数之前
- `pdf_extract_text`: 将 `ctx` 移到 `page_range` 前
- `sqlite_inspect_database`: 将 `ctx` 移到可选参数前
- `sqlite_query`: 将 `ctx` 移到 `params` 前
### Changed
- 更新文档以反映当前实现状态
- `TRD.md`: 更新项目结构、参数设计、实现状态
- `docs/API.md`: 示例改为平铺参数调用
- `README.md`: 版本号、项目结构、开发命令更新
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 · 111 lines · 0 tokens per session scan A 670c40e4bf90
update-changelog is a command published in the GitHub repository Asheng008/unifiles-mcp (0 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,295 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 commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
ship
Deploy feature through automated staging validation to production with rollback testing.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.