release-note

changes.md를 릴리즈 노트 형식으로 변환

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.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/JiHong88/suneditor --skill release-note

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

name	release-note
description	changes.md를 릴리즈 노트 형식으로 변환

Read changes.md and write a release note to release-note.md.

Follow the style and rules defined in prompts/release-note.md exactly.

Steps:

Read prompts/release-note.md for formatting rules
Read package.json to get the current version
Read changes.md for current change entries
Read release-note.md for existing release notes
Rewrite every changes.md entry into the release note format — one sentence each, with the source-file references ((`core/logic/shell/ui`)), root cause, and internal identifiers removed. Never copy an entry through unchanged; see "Condense First" in the rules.
Write ## <version> section to release-note.md
- If the top section already has the same version, replace that section
- If the top section has a different version, clear the entire file and write only the new version section
Clear changes.md contents (keep the file, empty the content)

Before writing, check the draft: no (`path/to/file`) references, no internal method or CSS selector names, no item longer than one sentence.

수동 코드 수정 후 changes.md에 누락된 변경사항 추가

코드 리뷰 — 버그, 로직 오류, dead code 검출

커밋 메시지를 자동 생성하고 커밋한다. 커밋 요청 시 반드시 이 스킬을 참조한다.

name	release-note
description	changes.md를 릴리즈 노트 형식으로 변환

Read changes.md and write a release note to release-note.md.

Follow the style and rules defined in prompts/release-note.md exactly.

Steps:

Read prompts/release-note.md for formatting rules
Read package.json to get the current version
Read changes.md for current change entries
Read release-note.md for existing release notes
Rewrite every changes.md entry into the release note format — one sentence each, with the source-file references ((`core/logic/shell/ui`)), root cause, and internal identifiers removed. Never copy an entry through unchanged; see "Condense First" in the rules.
Write ## <version> section to release-note.md
- If the top section already has the same version, replace that section
- If the top section has a different version, clear the entire file and write only the new version section
Clear changes.md contents (keep the file, empty the content)

Before writing, check the draft: no (`path/to/file`) references, no internal method or CSS selector names, no item longer than one sentence.