@simplysm/sd-claude 13.0.48 → 13.0.50

package/claude/skills/sd-debug/SKILL.md

@@ -63,11 +63,12 @@ You MUST complete each phase before proceeding to the next.
    - Does it happen every time?
    - If not reproducible → gather more data, don't guess
 
-3. **Check Recent Changes**
-   - What changed that could cause this?
-   - Git diff, recent commits
-   - New dependencies, config changes
-   - Environmental differences
+3. **Read the Source Code Directly**
+   - Read the actual code where the bug manifests
+   - Understand what the code does line by line
+   - Walk through the logic with the failing input mentally
+   - Do NOT run `git diff` or `git log` — diffs show WHAT changed, not WHY it's broken
+   - The bug is in the code as it exists NOW; analyze the code as-is
 
 4. **Gather Evidence in Multi-Component Systems**
 
@@ -224,6 +225,7 @@ If you catch yourself thinking:
 - "Pattern says X but I'll adapt it differently"
 - "Here are the main problems: [lists fixes without investigation]"
 - Proposing solutions before tracing data flow
+- "Let me check git diff/log to see what changed"
 - **"One more fix attempt" (when already tried 2+)**
 - **Each fix reveals new problem in different place**
 
@@ -253,13 +255,14 @@ If you catch yourself thinking:
 | "Multiple fixes at once saves time" | Can't isolate what worked. Causes new bugs. |
 | "Reference too long, I'll adapt the pattern" | Partial understanding guarantees bugs. Read it completely. |
 | "I see the problem, let me fix it" | Seeing symptoms ≠ understanding root cause. |
+| "Let me check git diff to see what changed" | Diff shows WHAT changed, not WHY it's broken. Read the code as-is. |
 | "One more fix attempt" (after 2+ failures) | 3+ failures = architectural problem. Question pattern, don't fix again. |
 
 ## Quick Reference
 
 | Phase | Key Activities | Success Criteria |
 |-------|---------------|------------------|
-| **1. Root Cause** | Read errors, reproduce, check changes, gather evidence | Understand WHAT and WHY |
+| **1. Root Cause** | Read errors, reproduce, read source code, gather evidence | Understand WHAT and WHY |
 | **2. Pattern** | Find working examples, compare | Identify differences |
 | **3. Hypothesis** | Form theory, test minimally | Confirmed or new hypothesis |
 | **4. Implementation** | Create test, fix, verify | Bug resolved, tests pass |

package/claude/skills/sd-plan/SKILL.md

@@ -160,7 +160,7 @@ You can start from any step or skip steps as needed.
   - Briefly explain why (1 sentence)
 - Do NOT auto-proceed. Wait for user's choice.
 
-**Yolo mode:** If the user responds with "Path A: yolo" or "Path B: yolo" (or similar intent like "A yolo", "B 자동"), execute all steps of the chosen path sequentially without stopping between steps.
+**Yolo mode:** If the user responds with "Path A: yolo" or "Path B: yolo" (or similar intent like "A yolo", "B 자동"), execute all steps of the chosen path sequentially without stopping between steps. **Each `/sd-*` step MUST be invoked via the Skill tool** (e.g., `Skill("sd-worktree", "add <name>")`, `Skill("sd-plan-dev")`, `Skill("sd-check")`, `Skill("sd-commit")`, `Skill("sd-worktree", "merge")`, `Skill("sd-worktree", "clean")`). Do NOT execute the underlying git/shell commands directly — always delegate to the skill.
 
 **Yolo sd-check — include dependents:** NEVER check only modified packages. Also check all packages that depend on them:
 1. Identify modified packages from `git diff --name-only`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@simplysm/sd-claude",
-  "version": "13.0.48",
+  "version": "13.0.50",
   "description": "Simplysm Claude Code CLI — asset installer and cross-platform npx wrapper",
   "author": "김석래",
   "license": "Apache-2.0",