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.
Datos de origen
- Repositorio
- Bilal140202/skillproof
- Última actividad en el origen
- 27 de septiembre de 2026 a las 03:53
- Idioma detectado de SKILL.md
- inglés
- Estrellas
- 0
- Forks
- 0
Opciones de instalación
De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.
Revisa los archivos de origen
Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.
Mostrando SKILL.md
SKILL.md
Instrucciones de origen · Vista previa de solo lectura- 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).
Ver en GitHub