Pdlc changelog
更新变更日志From its SKILL.md
npx -y skills add kanfu-panda/pdlc-skills --skill pdlc-changelogAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
- runs commandsInstructs the agent to run 1 command, including `git log`.
SKILL.md
1.3 KB, 365 tokens by cl100k_base, as published. Nobody here has run it
更新变更日志
<!-- @include templates/prompts/iron-law.md -->根据最近的 git 提交记录，更新指定服务或应用的 CHANGELOG.md。
工作流程
- 运行
git log查看最近的提交记录 - 按约定式提交分类：feat / fix / docs / chore / refactor / test
- 更新对应服务/应用的
CHANGELOG.md，使用templates/changelog-template.md作为格式与分节模板 - 遵循 Keep a Changelog 格式
分类规则
- 新增（Added）: feat 类型的提交
- 修复（Fixed）: fix 类型的提交
- 变更（Changed）: refactor 类型的提交
- 移除（Removed）: 删除功能相关的提交
- 文档（Docs）: docs 类型的提交
要求
<!-- @include templates/prompts/output-language.md -->- 每条记录简洁明了，描述"做了什么"和"为什么"
- 如果涉及破坏性变更，需特别标注
目标: $ARGUMENTS
<!-- @include templates/prompts/handoff.md -->本命令的 handoff 输出：
✅ 变更日志 完成
📦 产出：CHANGELOG.md
👉 下一步：（本次流程结束，无后续）
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 3 of the 12 instructions most readme changelog skills give in 365 tokens
Counted across 446 of the 460 authors here whose files we hold, read 2026-09-06
- Follow Keep a Changelog formathere, and in 24 of 446
- Collect commits since the last git tagin 15 of 446, across 13 files
- Omit empty sectionsin 14 of 446
- Put breaking changes first with migration stepsin 14 of 446
- Include migration guidance for breaking changesin 11 of 446, across 10 files
- Categorize commits by conventional commit prefixhere, and in 11 of 446
- Mark breaking changes prominentlyhere, and in 10 of 446
- Prepend the new entry to CHANGELOG.mdin 9 of 446
- Highlight breaking changes with migration notesin 8 of 446, across 7 files
- Classify changes into Keep a Changelog categoriesin 8 of 446, across 7 files
- Group related commits into single entriesin 8 of 446
- Write the changelog from commitsin 8 of 446
Said here and by no other author read
- update the target service's CHANGELOG.md
- keep each entry concise, stating what and why
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.