(.claude): ⚙️ changeset-generator 스킬에 commit hash prefix 대응 가이드 추가

pnpm changeset version이 changeset 본문을 '- <hash>: <content>' 형태로
감싸는 점을 고려하여 SKILL.md의 포맷 가이드를 업데이트한다.
'### 헤딩', 빈 줄, 다단락 본문은 리스트 아이템을 깨뜨리므로 금지하고
한 줄 평문 불릿 형태로 작성하도록 명시한다.

Author: puffcocos

.claude/skills/changeset-generator/SKILL.md

@@ -22,7 +22,7 @@ This skill replaces `pnpm changeset add` by automatically analyzing git changes
    - Bug fixes, dependency bumps → `patch`
    - Docs/CI/refactor with no API impact → excluded by default
 3. **Asks how to group**: When multiple packages are changed, asks the user whether to bundle them into a single changeset or create separate changeset files per package
-4. **Writes user-friendly description**: Transforms commit messages into clear release notes with code examples for breaking changes or new APIs
+4. **Writes user-friendly description**: Transforms commit messages into a flat list of plain-sentence bullets (one per change) that render cleanly after the changelog's `- <commit-hash>:` prefix
 5. **Creates the changeset file(s)**: Writes to `.changeset/<slug>.md` and shows it for review before committing
 
 ## How to Use
@@ -35,34 +35,28 @@ Analyzes all commits since branching from `main` and generates the changeset fil
 
 ## Changeset File Format
 
+**IMPORTANT:** `pnpm changeset version` wraps every changeset body line as `- <commit-hash>: <content>` in the generated `CHANGELOG.md`. This means markdown headings (`###`), blank lines, and multi-paragraph content inside a changeset body will render as a broken list item. Keep the body as a flat list of plain sentences — one bullet per change — and do NOT use headings or section labels.
+
+Good format (renders cleanly under `- abc1234: ...`):
+
 ````md
 ---
 "@scope/package-a": minor
 "@scope/package-b": patch
 ---
 
-### Breaking Changes
-
-- Description with before/after code examples
-
-  ```ts
-  // Before
-  import foo from "@scope/package-a/old-name";
-
-  // After
-  import foo from "@scope/package-a/new-name";
-  ```
+- Rename `@scope/package-a/old-name` export to `@scope/package-a/new-name`. Update imports to use the new path.
+- Add new helper `formatFoo()` in `@scope/package-b` for formatting foo values.
+- Fix crash in `@scope/package-a` when config is undefined.
 ````
 
-### New Features
+Guidelines for each bullet:
 
-- Description with usage example
-
-### Bug Fixes
-
-- Description
-
-```
+- Write one self-contained sentence per change. If context is needed, add it inline — do not split across lines or paragraphs.
+- Lead with the action verb (Add / Fix / Rename / Remove / Update).
+- Mention affected exports, APIs, or files inline using backticks so the changelog is searchable.
+- For breaking changes, state the before → after inline (e.g., "Rename `X` to `Y`") rather than using a separate heading.
+- Do not use `###`, `**bold labels**`, blockquotes, or fenced code blocks inside the body — they will break the wrapped list item.
 
 ## Example