From 5e8e42fb74f8de413cce6a8dd5989a6e0a6a7dce Mon Sep 17 00:00:00 2001
From: YeonGyu-Kim <code.yeon.gyu@gmail.com>
Date: Sun, 14 Dec 2025 12:44:48 +0900
Subject: [PATCH] fix(command): improve /get-unpublished-changes output clarity
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

- Enforce immediate output without questions
- Require actual diff analysis instead of commit message copying
- Unify output format across all change types
- Remove emojis from section headers

🤖 GENERATED WITH ASSISTANCE OF [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode)
---
 .opencode/command/get-unpublished-changes.md | 56 +++++++++++++++-----
 1 file changed, 43 insertions(+), 13 deletions(-)

diff --git a/.opencode/command/get-unpublished-changes.md b/.opencode/command/get-unpublished-changes.md
index 5fd797b..4bad000 100644
--- a/.opencode/command/get-unpublished-changes.md
+++ b/.opencode/command/get-unpublished-changes.md
@@ -4,13 +4,25 @@ model: anthropic/claude-haiku-4-5
 ---
 
 <command-instruction>
-Analyze the unpublished changes since the last npm release and provide a structured summary.
+IMMEDIATELY output the analysis. NO questions. NO preamble.
 
-Your task:
-1. Review the context below (auto-injected via shell)
-2. Summarize changes grouped by type (feat, fix, refactor, docs, chore)
-3. Highlight breaking changes if any
-4. Suggest next version bump (major/minor/patch) based on conventional commits
+## CRITICAL: DO NOT just copy commit messages!
+
+For each commit, you MUST:
+1. Read the actual diff to understand WHAT CHANGED
+2. Describe the REAL change in plain language
+3. Explain WHY it matters (if not obvious)
+
+## Steps:
+1. Run `git diff v{published-version}..HEAD` to see actual changes
+2. Group by type (feat/fix/refactor/docs) with REAL descriptions
+3. Note breaking changes if any
+4. Recommend version bump (major/minor/patch)
+
+## Output Format:
+- feat: "Added X that does Y" (not just "add X feature")
+- fix: "Fixed bug where X happened, now Y" (not just "fix X bug")
+- refactor: "Changed X from A to B, now supports C" (not just "rename X")
 </command-instruction>
 
 <version-context>
@@ -40,15 +52,33 @@ Your task:
 <output-format>
 ## Unpublished Changes (v{published} → HEAD)
 
-### Commits ({count})
-| Type | Scope | Description |
-|------|-------|-------------|
-| ... | ... | ... |
+### feat
+| Scope | What Changed |
+|-------|--------------|
+| X | 실제 변경 내용 설명 |
+
+### fix
+| Scope | What Changed |
+|-------|--------------|
+| X | 실제 변경 내용 설명 |
+
+### refactor
+| Scope | What Changed |
+|-------|--------------|
+| X | 실제 변경 내용 설명 |
+
+### docs
+| Scope | What Changed |
+|-------|--------------|
+| X | 실제 변경 내용 설명 |
+
+### Breaking Changes
+None 또는 목록
 
 ### Files Changed
-{diff-stat summary}
+{diff-stat}
 
 ### Suggested Version Bump
-- **Recommendation**: {patch|minor|major}
-- **Reason**: {brief explanation}
+- **Recommendation**: patch|minor|major
+- **Reason**: 이유
 </output-format>