@simplysm/sd-claude 13.0.78 → 13.0.80

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

@@ -1,67 +0,0 @@
----
-name: sd-use
-description: "Route requests to sd-* skills/agents (explicit invocation only)"
-model: haiku
----
-
-# sd-use - Auto Skill Router
-
-Analyze user request from ARGUMENTS, select the best matching skill, explain why, then execute it.
-
-## Execution Flow
-
-1. Read ARGUMENTS
-2. If user names a specific skill, route to that skill directly
-3. Otherwise, match against catalog below
-4. Report selection with reason
-5. Execute immediately
-
-## Catalog (execute via `Skill` tool)
-
-| Skill                | When to select                                                                                                                                  |
-|----------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|
-| `sd-brainstorm`      | New feature, component, or behavior change — **creative work before implementation**                                                            |
-| `sd-debug`           | Bug, test failure, unexpected behavior — **systematic root cause investigation**                                                                |
-| `sd-tdd`             | Implementing a feature or fixing a bug — **before writing code**                                                                                |
-| `sd-plan`            | Multi-step task with spec/requirements — **planning before code**                                                                               |
-| `sd-plan-dev`        | Already have a plan — **executing implementation plan**                                                                                         |
-| `sd-review`          | Code review + refactoring analysis — defects, safety, API design, conventions, complexity, duplication, code structure                           |
-| `sd-check`           | Verify code — typecheck, lint, tests                                                                                                            |
-| `sd-commit`          | Create a git commit                                                                                                                             |
-| `sd-readme`          | Update a package README.md                                                                                                                      |
-| `sd-discuss`         | Evaluate code design decisions against industry standards and project conventions                                                                |
-| `sd-api-name-review` | Review public API naming consistency                                                                                                            |
-| `sd-worktree`        | Start new work in branch isolation                                                                                                              |
-| `sd-skill`           | Create or edit skills                                                                                                                           |
-| `sd-email-analyze`   | Analyze, read, or summarize email files (`.eml` or `.msg`) — parsing and attachment extraction                                                  |
-| `sd-document`        | Read or write document files (`.docx`, `.xlsx`, `.pptx`, `.pdf`) — content extraction, creation, data export                                    |
-
-## Selection Rules
-
-1. **Explicit skill name** — If user mentions a specific skill name, route to that skill directly
-2. Select **exactly one** skill — the most specific match wins
-3. **Review & Refactor**: "find bugs", "review", "refactor", "improve structure", "remove duplication" → `sd-review`
-4. **Sequential requests**: Route to the **first** skill only. After completion, user can invoke the next
-5. If nothing matches, use **default LLM behavior** and handle the request directly
-6. Pass ARGUMENTS through as the skill's input
-
-## Report Format
-
-Before executing, output:
-
-```
-**Selected**: `{skill-name}`
-**Reason**: {one-line explanation}
-**Tip**: Next time you can call `/{skill-name} {request}` directly.
-```
-
-Then execute immediately.
-
-If no match:
-
-```
-**Selected**: Default LLM
-**Reason**: {one-line explanation}
-```
-
-Then handle the request directly.

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

@@ -1,78 +0,0 @@
----
-name: sd-worktree
-description: "Git worktree branch isolation (explicit invocation only)"
-model: haiku
----
-
-# sd-worktree
-
-Branch-isolated workflow using git worktrees.
-
-## Flow
-
-```mermaid
-flowchart TD
-    START([sd-worktree invoked]) --> ADD
-
-    subgraph ADD [add]
-        A1["git worktree add .worktrees/NAME -b NAME"]
-        A1 -->|fail| HALT
-        A1 -->|ok| A2[detect package manager]
-        A2 --> A3["pm install (cwd: .worktrees/NAME)"]
-        A3 -->|fail| HALT
-        A3 -->|ok| A4["cd .worktrees/NAME"]
-    end
-
-    A4 --> WORK["work + commit inside worktree"]
-    WORK --> MERGE
-
-    subgraph MERGE [merge]
-        M0["cd PROJECT_ROOT"]
-        M0 --> M1["git merge NAME --no-ff (cwd: PROJECT_ROOT)"]
-        M1 -->|fail| HALT
-        M1 -->|ok| M2[merge complete]
-    end
-
-    M2 --> CLEAN
-
-    subgraph CLEAN [clean]
-        C1{"cwd inside worktree?"}
-        C1 -->|yes| HALT
-        C1 -->|no| C2["rm -rf .worktrees/NAME (bash)"]
-        C2 --> C3["git worktree prune"]
-        C3 --> C4["git branch -d NAME"]
-        C4 -->|fail| HALT
-        C4 -->|ok| C5[done]
-    end
-
-    HALT([HALT - AskUserQuestion])
-```
-
-## Rules
-
-### HALT
-
-When any step reaches **fail** or **HALT**:
-
-1. Show the error message to the user as-is
-2. Ask the user how to proceed via `AskUserQuestion`
-3. Do **nothing** until the user responds
-
-Manual git merge, git stash, git reset, git clean, or **any workaround is forbidden**. Yolo mode does NOT override HALT.
-
-### Worktree location
-
-All worktrees MUST be created under **`.worktrees/`** (project root).
-
-### Package manager detection
-
-| File | PM |
-|---|---|
-| `pnpm-lock.yaml` | pnpm |
-| `yarn.lock` | yarn |
-| `package-lock.json` | npm |
-| `bun.lockb` / `bun.lock` | bun |
-
-### clean: use rm -rf
-
-`git worktree remove` almost always fails on Windows due to file locks. Use `rm -rf` (bash) + `git worktree prune` instead.