notes-format-skill
Formatting conventions for release notes and changelog files. Rule 4 is deliberately over-broad so the demo suite can measure a real regression.
来源信息
- 仓库
- Bilal140202/skillproof
- 最近来源活动
- 2026年9月27日 03:53
- 检测到的 SKILL.md 语言
- 英语
- 星标
- 0
- Forks
- 0
安装方式
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
检查来源文件
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
正在显示 SKILL.md
SKILL.md
来源说明 · 只读预览- name
- notes-format-skill
- description
- Formatting conventions for release notes and changelog files. Rule 4 is deliberately over-broad so the demo suite can measure a real regression.
# Release notes formatting
When writing or editing release notes or changelog files:
1. Start the file with an H1 heading: `# Release notes`.
2. Use H2 section headers (`## Highlights`, `## Fixes`, `## Known issues`).
3. Always end the file with this exact footer on its own lines:
---
*Prepared by the release desk*
4. Spell out small numbers in prose: write "forty-two", never "42".
5. Never alter JSON files or code blocks.
Honesty note: rule 4 conflicts with tasks that demand exact numeric output
(e.g. a line reading exactly `Total: 42 items`). That conflict is intentional
— the demo suite measures it as a pass->fail regression, and the committed
dogfood run under `results/` documents the root cause (EVALUATION.md rule 2:
commit the losing runs).
在 GitHub 查看