claude-plugin-viban 1.0.30 → 1.0.32

package/bin/viban

@@ -77,11 +77,15 @@ auto_update_check() {
     # Compare and auto-update if newer version available
     if [[ -n "$cached_latest" && "$cached_latest" != "$current" ]]; then
         # Simple semver comparison: split on dots and compare numerically
-        local IFS='.'
-        local -a cv=($current) lv=($cached_latest)
-        local is_newer=false
+        local -a cv lv
+        cv=("${(@s/./)current}")
+        lv=("${(@s/./)cached_latest}")
+        local is_newer=false c l
         for i in 1 2 3; do
-            local c=${cv[$i]:-0} l=${lv[$i]:-0}
+            c=${cv[$i]:-0}; l=${lv[$i]:-0}
+            # Strip non-numeric suffixes (e.g. 1-beta -> 1)
+            c=${c%%[^0-9]*}; l=${l%%[^0-9]*}
+            [[ -z "$c" ]] && c=0; [[ -z "$l" ]] && l=0
             if (( l > c )); then
                 is_newer=true
                 break
@@ -156,6 +160,16 @@ VIBAN_JSON="${VIBAN_DATA_DIR}/viban.json"
 # Ensure data directory exists
 mkdir -p "$VIBAN_DATA_DIR"
 
+# Auto-migrate: .viban/viban.json -> .git/ when git repo is initialized
+if $VIBAN_IS_GIT_REPO; then
+    _legacy_json="${PWD}/.viban/viban.json"
+    if [[ -f "$_legacy_json" && ! -f "$VIBAN_JSON" ]]; then
+        mv "$_legacy_json" "$VIBAN_JSON"
+        rmdir "${PWD}/.viban" 2>/dev/null
+        echo "✓ Migrated viban data from .viban/ to git directory"
+    fi
+fi
+
 # ============================================================
 # Initialize viban.json if not exists
 # ============================================================
@@ -247,7 +261,9 @@ update_term_cache() {
         CACHED_TERM_H=$(tput lines 2>/dev/null || echo 30)
     fi
     CACHED_COL_W=$(( (CACHED_TERM_W - 2) / 3 ))
-    CACHED_MAX_H=$((CACHED_TERM_H - 8))
+    local _header_extra=0
+    $VIBAN_IS_GIT_REPO || _header_extra=1
+    CACHED_MAX_H=$((CACHED_TERM_H - 8 - _header_extra))
     CACHED_MAX_TASKS=$((CACHED_MAX_H / 5))
     (( CACHED_MAX_TASKS < 2 )) && CACHED_MAX_TASKS=2
     (( CACHED_MAX_TASKS > 8 )) && CACHED_MAX_TASKS=8
@@ -500,7 +516,40 @@ print_center() {
 draw_header() {
     printf '\033[K\n'
     print_center "VIBAN" "${A_BOLD}${A_ACCENT}"
-    print_center "Vibe Kanban" "${A_DIM}"
+    local _ver repo_name subtitle="Vibe Kanban"
+    _ver=$(grep '"version"' "$VIBAN_SCRIPT_DIR/package.json" 2>/dev/null | sed 's/.*: *"\([^"]*\)".*/\1/')
+    repo_name=$(basename "$(git rev-parse --show-toplevel 2>/dev/null)" 2>/dev/null)
+    [[ -n "$repo_name" ]] && subtitle="Vibe Kanban · $repo_name"
+    if [[ -n "$_ver" ]]; then
+        subtitle="$subtitle · v$_ver"
+        # Check for update availability from cache
+        if [[ -f "$_VIBAN_UPDATE_CACHE" ]]; then
+            local cached_latest
+            cached_latest=$(sed -n '2p' "$_VIBAN_UPDATE_CACHE" 2>/dev/null)
+            if [[ -n "$cached_latest" && "$cached_latest" != "$_ver" ]]; then
+                local -a cv lv
+                cv=("${(@s/./)_ver}")
+                lv=("${(@s/./)cached_latest}")
+                local _is_newer=false _c _l
+                for i in 1 2 3; do
+                    _c=${cv[$i]:-0}; _l=${lv[$i]:-0}
+                    _c=${_c%%[^0-9]*}; _l=${_l%%[^0-9]*}
+                    [[ -z "$_c" ]] && _c=0; [[ -z "$_l" ]] && _l=0
+                    if (( _l > _c )); then
+                        _is_newer=true
+                        break
+                    elif (( _l < _c )); then
+                        break
+                    fi
+                done
+                $_is_newer && subtitle="$subtitle → v$cached_latest"
+            fi
+        fi
+    fi
+    print_center "$subtitle" "${A_DIM}"
+    if ! $VIBAN_IS_GIT_REPO; then
+        print_center "⚠ Not a git repo · assign/PR unavailable" "${A_DIM}"
+    fi
     printf '\033[K\n'
 }
 

package/commands/{task.md → add.md}

@@ -2,7 +2,7 @@
 description: "Analyze problem and register as viban issue with evidence"
 ---
 
-# /task - Problem Analysis and Issue Registration
+# /add - Problem Analysis and Issue Registration
 
 Analyze problem situation and register as viban issue with file locations and evidence.
 

package/commands/release.md

@@ -0,0 +1,99 @@
+---
+description: "Bump version, commit, tag, and push to trigger npm publish"
+---
+
+# /release - Release a new version
+
+Bump the package version, commit, tag, and push to trigger the automated npm publish workflow.
+
+## Execution Steps
+
+### Step 1: Pre-flight checks
+
+```bash
+# Ensure on main branch
+git branch --show-current  # must be "main"
+
+# Ensure working tree is clean (no uncommitted changes)
+git status --porcelain
+
+# Ensure up to date with remote
+git fetch origin main
+git diff origin/main --stat
+```
+
+If not on main, working tree is dirty, or behind remote: **stop and inform user**.
+
+### Step 2: Determine version bump
+
+Read current version from `package.json`:
+
+```bash
+grep '"version"' package.json
+```
+
+Ask user with AskUserQuestion:
+- header: "Version"
+- question: "Current version is {current}. What kind of bump?"
+- options:
+  - "patch" (x.y.Z) - bug fixes, small changes
+  - "minor" (x.Y.0) - new features, backward compatible
+  - "major" (X.0.0) - breaking changes
+- multiSelect: false
+
+Calculate the new version based on selection.
+
+### Step 3: Show changelog preview
+
+Show commits since last tag:
+
+```bash
+git log $(git describe --tags --abbrev=0)..HEAD --oneline
+```
+
+Display to user for confirmation before proceeding.
+
+### Step 4: Run tests
+
+```bash
+zsh tests/run_all.zsh
+```
+
+If tests fail: **stop and inform user**. Do not release with failing tests.
+
+### Step 5: Bump version and release
+
+```bash
+# Update package.json version
+# (use jq or sed to update the version field)
+
+# Commit
+git add package.json
+git commit -m "{new_version}"
+
+# Tag
+git tag v{new_version}
+
+# Push with tags
+git push origin main --tags
+```
+
+### Step 6: Confirm
+
+```
+╭──────────────────────────────────────╮
+│  Released v{new_version}!            │
+╰──────────────────────────────────────╯
+
+- npm publish: triggered via GitHub Actions
+- GitHub Release: auto-generated with release notes
+
+Check: https://github.com/happy-nut/claude-plugin-viban/actions
+```
+
+## Error Handling
+
+- **Not on main**: "Switch to main branch first"
+- **Dirty working tree**: "Commit or stash changes first"
+- **Tests failing**: "Fix failing tests before release"
+- **Push failed**: "Check remote access and try again"

package/docs/CLAUDE.md

@@ -29,6 +29,14 @@ EOF
 - 스피너 있을 때/없을 때 둘 다 확인
 - 한글 포함 제목 truncation
 
+## Release Rules
+
+**릴리즈는 사용자가 명시적으로 요청할 때만 수행한다.**
+
+- 버전 범프, git tag, git push --tags 를 자동으로 하지 않는다
+- 사용자가 `/viban:release` 또는 "릴리즈 해줘" 라고 할 때만 수행
+- 커밋은 자유롭게 하되, 릴리즈(버전 범프 + 태그 + 푸시)는 반드시 사용자 승인 후
+
 ## Workflow Rules
 
 ### 🔴 Worktree 사용 금지

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-plugin-viban",
-  "version": "1.0.30",
+  "version": "1.0.32",
   "description": "Terminal Kanban TUI for AI-human collaborative issue tracking",
   "main": "bin/viban",
   "bin": {

package/skills/{task → add}/SKILL.md

@@ -1,10 +1,10 @@
 ---
-name: task
+name: add
 description: "Analyze problem and register as viban issue with evidence"
 enter_plan_mode: true
 ---
 
-# /task - Problem Analysis and Issue Registration
+# /add - Problem Analysis and Issue Registration
 
 Analyze problem situation and register as viban issue with file locations and evidence.
 
@@ -183,7 +183,7 @@ Next steps:
 
 ## Example Interview Flow
 
-**User runs**: `/viban:task`
+**User runs**: `/viban:add`
 
 **Agent**: (AskUserQuestion)
 ```

package/skills/release/SKILL.md

@@ -0,0 +1,100 @@
+---
+name: release
+description: "Bump version, commit, tag, and push to trigger npm publish"
+---
+
+# /release - Release a new version
+
+Bump the package version, commit, tag, and push to trigger the automated npm publish workflow.
+
+## Execution Steps
+
+### Step 1: Pre-flight checks
+
+```bash
+# Ensure on main branch
+git branch --show-current  # must be "main"
+
+# Ensure working tree is clean (no uncommitted changes)
+git status --porcelain
+
+# Ensure up to date with remote
+git fetch origin main
+git diff origin/main --stat
+```
+
+If not on main, working tree is dirty, or behind remote: **stop and inform user**.
+
+### Step 2: Determine version bump
+
+Read current version from `package.json`:
+
+```bash
+grep '"version"' package.json
+```
+
+Ask user with AskUserQuestion:
+- header: "Version"
+- question: "Current version is {current}. What kind of bump?"
+- options:
+  - "patch" (x.y.Z) - bug fixes, small changes
+  - "minor" (x.Y.0) - new features, backward compatible
+  - "major" (X.0.0) - breaking changes
+- multiSelect: false
+
+Calculate the new version based on selection.
+
+### Step 3: Show changelog preview
+
+Show commits since last tag:
+
+```bash
+git log $(git describe --tags --abbrev=0)..HEAD --oneline
+```
+
+Display to user for confirmation before proceeding.
+
+### Step 4: Run tests
+
+```bash
+zsh tests/run_all.zsh
+```
+
+If tests fail: **stop and inform user**. Do not release with failing tests.
+
+### Step 5: Bump version and release
+
+```bash
+# Update package.json version
+# (use jq or sed to update the version field)
+
+# Commit
+git add package.json
+git commit -m "{new_version}"
+
+# Tag
+git tag v{new_version}
+
+# Push with tags
+git push origin main --tags
+```
+
+### Step 6: Confirm
+
+```
+╭──────────────────────────────────────╮
+│  Released v{new_version}!            │
+╰──────────────────────────────────────╯
+
+- npm publish: triggered via GitHub Actions
+- GitHub Release: auto-generated with release notes
+
+Check: https://github.com/happy-nut/claude-plugin-viban/actions
+```
+
+## Error Handling
+
+- **Not on main**: "Switch to main branch first"
+- **Dirty working tree**: "Commit or stash changes first"
+- **Tests failing**: "Fix failing tests before release"
+- **Push failed**: "Check remote access and try again"