release-note

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

インストール方法

デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。

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

コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。

ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。

インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。

SKILL.md

ソースの指示 · 読み取り専用プレビュー

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.