.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "jsc-git",
-  "version": "0.0.1",
+  "version": "0.0.2",
   "description": "Commit 分組認可與 Push Request 建立",
   "skills": "./skills",
   "author": {

.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "jsc-git",
-  "version": "0.0.1",
+  "version": "0.0.2",
   "description": "Commit 分組認可與 Push Request 建立",
   "skills": "./skills"
 }

plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "jsc-git",
-  "version": "0.0.1",
+  "version": "0.0.2",
   "description": "Commit 分組認可與 Push Request 建立",
   "skills": "./skills/"
 }

skills/pr/SKILL.md

@@ -12,7 +12,7 @@ description: Commit all changes via jsc-git:commit, create a target branch named
 3. Create the target branch from the remote base branch:
    1. Take the type with the highest priority across all commits: `revert > fix > feat > perf > refactor > test > docs > style > chore`.
    2. Summarize one title from all commit messages.
-   3. Branch names allow **ASCII only**; always slugify as `{type}/{requirement or feature}-{title}`. Translate the requirement and title into a short English phrase first, then lowercase, replace every character outside `a-z0-9` with a hyphen, collapse consecutive hyphens, and trim leading and trailing hyphens (example: `feat/order-匯出報表` → `feat/order-export-report`). No spaces, parentheses, colons, or any non-ASCII character.
+   3. Branch names allow **ASCII only**; always slugify as `{type}/{requirement or feature}-{title}`. Translate the requirement and title into a short English phrase first, then call `tools/slugify.sh {type} {phrase}` to produce the final slug (example: translate a non-English request to English first, then slugify — "export report" → export-report → feat/order-export-report). No spaces, parentheses, colons, or any non-ASCII character.
 4. Run `git push -u origin {target branch}`.
 5. Create the PR: `jsc-gitea/tools/gitea.sh pr-create {owner}/{repo} {target branch} {base branch} "{branch name}" {description file}`.
    - Title = branch name.
@@ -26,4 +26,4 @@ description: Commit all changes via jsc-git:commit, create a target branch named
 
 1. No template section may stay empty: fill the literal 「無」 when there is no plan page, analyze page, or prerequisite PR.
 2. Take the plan page and analyze page links from the `jsc-sdlc` wiki pages; the analyze link must point at the work package heading anchor.
-3. The description drafting details **MUST run as a sub agent**.
+3. Branch title summarization (step 3.2) and description drafting MUST run as a sub agent.

tools/slugify.sh

@@ -0,0 +1,20 @@
+#!/usr/bin/env sh
+# slugify.sh — 把分支類型與描述轉成 ASCII 分支名 slug。
+# 用法: slugify.sh {type} {phrase}
+# 規則: 全部轉小寫，非 a-z0-9 的字元換成連字號，
+#       連續連字號合併成一個，並去除開頭與結尾的連字號。
+# 輸出: {type}/{slug}（例如: slugify.sh feat "export report" → feat/export-report）
+set -u
+
+if [ "$#" -lt 2 ]; then
+  echo "用法: slugify.sh {type} {phrase}" >&2
+  exit 1
+fi
+
+TYPE="$1"
+shift
+PHRASE="$*"
+
+slug=$(printf '%s' "$PHRASE" | tr '[:upper:]' '[:lower:]' | sed -e 's/[^a-z0-9]/-/g' -e 's/-\{2,\}/-/g' -e 's/^-//' -e 's/-$//')
+
+printf '%s/%s\n' "$TYPE" "$slug"