Changes 技能测试
- 作者仓库星标 1,985
- 许可证 MIT
- 作者仓库 suneditor
The user has manually modified code and needs changes.md updated.
(When Claude modifies code, changes.md is updated automatically per CLAUDE.md instructions. This skill is only for user-initiated changes.)
Follow the rules defined in prompts/changes-guide.md exactly.
Steps:
- Read
prompts/changes-guide.mdfor formatting rules - Run
git diff --stagedandgit diffto find current changes - If no changes found, run
git diff HEAD~1for the last commit - Read the current
changes.md - Analyze the diff — classify each user-facing change as
feat,fix,change, orbreaking - Skip internal-only changes (
style,docs,test,chore,ci,build) - Add new entries to the appropriate section in
changes.md(do not duplicate existing entries) - If unsure about a change's classification, ask before adding
- 流狐分类
- 通用
- 作者声明 Agent
- 未找到明确声明；不据此推断已兼容或已测试
- 静态检查
- 94 / 100 · 启发式扫描，不代表运行安全
- 作者 / 版本 / 许可
- @JiHong88 · MIT
- 流狐 Token 估算
- 低消耗
- 流狐接入估算
- 即装即用
- 是否需要外部 API Key
- 未发现要求
- 检测到的系统要求
- 未声明
- 底层运行要求
- 未声明
- 检测到的文件与系统行为
-
- 只读
- 检测到的网络行为
- 仅限本地
- 安装命令数
- 无（仅作为资料）
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
作者没有在当前 SKILL.md 中定义固定输出样例。 原文未拆分步骤
The user has manually modified code and needs `changes.md` updated. (When Claude modifies code, `changes.md` is updated automatically per CLAUDE.md instructions. This skill is only for user-initiated changes.) Follow the rules defined in `prompts/changes-guide.md` exactly. Steps: …
The user has manually modified code and needs `changes.md` updated.
(When Claude modifies code, `changes.md` is updated automatically per CLAUDE.md instructions. This skill is only for user-initiated changes.)
Follow the rules defined in `prompts/changes-guide.md` exactly.
Steps:
1. Read `prompts/changes-guide.md` for formatting rules
2. Run `git diff --staged` and `git diff` to find current changes
3. If no changes found, run `git diff HEAD~1` for the last commit
4. Read the current `changes.md`
5. Analyze the diff — classify each user-facing change as `feat`, `fix`, `change`, or `breaking`
6. Skip internal-only changes (`style`, `docs`, `test`, `chore`, `ci`, `build`)
7. Add new entries to the appropriate section in `changes.md` (do not duplicate existing entries)
8. If unsure about a change's classification, ask before adding 证据边界与执行链路
作者原文负责流程事实；流狐只索引当前章节、要点、文件与命令。
章节 -> 原文未使用二、三级标题
要点 -> The user has manually modified code and needs changes.md updated. · Follow the rules defined in prompts/changes-guide.md exactly. · Steps: 1.
文件/命令 -> changes.md · prompts/changes-guide.md · git diff --staged · git diff · git diff HEAD~1 · feat · fix · change
内容 SHA-256 -> 3d1eb50dcdfc
原文结构
适用与边界
原文中的明确线索
changes.md、prompts/changes-guide.md、git diff --staged、git diff、git diff HEAD~1、feat、fix、change