chore: enhance release note command with grouping and context (#4795)

Author: yomybaby

.claude/commands/improve-release-note.md

@@ -21,12 +21,19 @@ You are an assistant that helps improve and format GitHub release notes for the
 - If given a release URL, extract the version and fetch the corresponding release
 - Use the `gh` command to get release information: `gh release view [version] --repo lablup/backend.ai-webui`
 
-### Step 2: Format According to Guidelines
-Follow the strict markdown format that categorizes changes by type:
+### Step 2: Analyze and Group Related Changes
+Before formatting, analyze the PRs to understand their purpose:
+- Review PR descriptions and linked Jira issues for context
+- Use `gh pr view [PR_NUMBER] --repo lablup/backend.ai-webui --json title,body,labels` to get detailed information
+- Group related changes within each category based on their purpose and impact
+- Check Jira issues when needed for additional context
+
+### Step 3: Format According to Guidelines
+Follow the markdown format that categorizes and groups changes:
 
 **Categories with emojis:**
 - ✨ Features (`feat`)
-- 🐛 Bug Fixes (`fix`) 
+- 🐛 Bug Fixes (`fix`)
 - 🔨 Refactoring (`refactor`)
 - 🛠 Chores (`chore`)
 - 🌐 i18n (`i18n`)
@@ -38,23 +45,36 @@ Follow the strict markdown format that categorizes changes by type:
 - ⚡ Performance (`perf`)
 - 🔧 Miscellaneous (`misc`)
 
-**Each item must:**
-- Be grouped under the correct category based on its prefix or content
+**Formatting requirements:**
+- **Group related items** within each category (e.g., "AI & Development", "File Management")
+- **Add contextual descriptions** (1-2 sentences) for each group explaining the changes and their impact
 - Show the FR issue number in bold (e.g., **FR-1002**) when available
 - Preserve the contributor info with `by @username`
 - Include the PR link in markdown inline format (e.g., [#1234](https://...))
 - Keep grouped PRs in a single line with all PRs inline, not multiline
 - Display version change in the title, e.g., `# What's Changed (v25.10.1 → v25.11.0)`
 - Always output in **English**
+- **Avoid exaggerated claims** like "5x faster" or "60% reduction" - use factual, professional language
 - Wrap the full output in triple backticks (```) for easy copy-paste
 
-### Step 3: Show Preview and Confirm
+**Example format:**
+```markdown
+## ✨ Features
+
+### AI & Development Experience Enhancements
+Enhanced integration with Claude Code and AI development tools. Added Backend.AI platform documentation skill for Claude Code and upgraded AI SDK to v5 with improved message handling.
+
+- **FR-1697**: add a claude skill references the backend.ai docs by @nowgnuesLee in [#4669](...)
+- **FR-1463**: upgrade AI SDK to v5 by @agatha197 in [#4697](...)
+```
+
+### Step 4: Show Preview and Confirm
 1. Display the improved release note format
 2. Ask for user confirmation before updating
 3. Wait for explicit approval (y/yes/confirm) before proceeding
 4. Only update the GitHub release after confirmation
 
-### Step 4: Update Release (After Confirmation)
+### Step 5: Update Release (After Confirmation)
 Use the `gh` command to update the release:
 ```bash
 gh release edit [version] --notes-file /tmp/improved-release-notes.md --repo lablup/backend.ai-webui