claude-plugin-viban 1.0.20 → 1.0.22

package/bin/viban

@@ -3,6 +3,9 @@
 # Requires: gum (brew install gum), jq
 setopt EXTENDED_GLOB
 
+# Store script directory at startup (before any function changes $0)
+VIBAN_SCRIPT_DIR="$(cd "$(dirname "$0")/.." && pwd)"
+
 # ============================================================
 # Dependency Check (Early exit with helpful messages)
 # ============================================================
@@ -95,7 +98,7 @@ EOF
 
 # Auto-initialize for commands that need data (not help/init)
 case "$1" in
-    help|--help|-h|init) ;;
+    help|--help|-h|--version|-v|init) ;;
     *) init_viban_json ;;
 esac
 
@@ -1072,20 +1075,27 @@ cmd_priority() {
 
 cmd_add() {
     init_json
-    [[ -z "$1" ]] && { echo "Usage: viban add \"title\" [\"description\"] [priority] [type]"; exit 1; }
+    [[ -z "$1" ]] && { echo "Usage: viban add \"title\" [\"description\"] [priority] [type] [attachments...]"; exit 1; }
     local id=$(get_next_id) now=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
     local desc="${2:-}"
     local priority="${3:-P3}"
     local issue_type="${4:-}"
+    shift 4 2>/dev/null || shift $#
+    local attachments=("$@")
     # Validate priority
     [[ ! "$priority" =~ ^P[0-3]$ ]] && priority="P3"
     # Validate type (bug, feat, chore, refactor)
     [[ -n "$issue_type" && ! "$issue_type" =~ ^(bug|feat|chore|refactor)$ ]] && issue_type=""
+    # Build attachments JSON array
+    local attachments_json="[]"
+    if [[ ${#attachments[@]} -gt 0 ]]; then
+        attachments_json=$(printf '%s\n' "${attachments[@]}" | jq -R . | jq -s .)
+    fi
     # New cards don't have order - they follow priority-based sorting
     # Order is only assigned when manually moved
     local tmpjson=$(mktemp)
     printf '%s' "$desc" > "$tmpjson"
-    jq --arg id "$id" --arg title "$1" --rawfile desc "$tmpjson" --arg priority "$priority" --arg issue_type "$issue_type" --arg now "$now" '
+    jq --arg id "$id" --arg title "$1" --rawfile desc "$tmpjson" --arg priority "$priority" --arg issue_type "$issue_type" --argjson attachments "$attachments_json" --arg now "$now" '
         .next_id = ((.next_id // 0) + 1) |
         .issues += [{
             id:($id|tonumber),
@@ -1094,6 +1104,7 @@ cmd_add() {
             status:"backlog",
             priority:$priority,
             type:(if $issue_type == "" then null else $issue_type end),
+            attachments:$attachments,
             assigned_to:null,
             created_at:$now,
             updated_at:$now
@@ -1101,7 +1112,9 @@ cmd_add() {
     rm -f "$tmpjson"
     local type_info=""
     [[ -n "$issue_type" ]] && type_info=" [$issue_type]"
-    echo "✓ #$id added ($priority)$type_info"
+    local attach_info=""
+    [[ ${#attachments[@]} -gt 0 ]] && attach_info=" +${#attachments[@]} files"
+    echo "✓ #$id added ($priority)$type_info$attach_info"
 }
 
 cmd_assign() {
@@ -1162,6 +1175,32 @@ cmd_done() {
 
 cmd_get() { init_json; jq --argjson id "$1" '.issues[]|select((.id|tonumber)==$id)' "$VIBAN_JSON"; }
 
+cmd_attach() {
+    init_json
+    [[ -z "$1" || -z "$2" ]] && { echo "Usage: viban attach <id> <file1> [file2...]"; exit 1; }
+    local id="$1"
+    shift
+    local files=("$@")
+
+    # Check if issue exists
+    local exists=$(jq --argjson id "$id" '[.issues[]|select((.id|tonumber)==$id)]|length' "$VIBAN_JSON")
+    [[ "$exists" == "0" ]] && { echo "Error: Issue #$id not found"; exit 1; }
+
+    # Build new attachments array
+    local new_attachments=$(printf '%s\n' "${files[@]}" | jq -R . | jq -s .)
+    local now=$(date -u +"%Y-%m-%dT%H:%M:%SZ")
+
+    # Merge with existing attachments
+    jq --argjson id "$id" --argjson new "$new_attachments" --arg now "$now" '
+        (.issues[] | select((.id|tonumber)==$id)) |= . + {
+            attachments: ((.attachments // []) + $new | unique),
+            updated_at: $now
+        }
+    ' "$VIBAN_JSON" > "$VIBAN_JSON.tmp" && mv "$VIBAN_JSON.tmp" "$VIBAN_JSON"
+
+    echo "✓ #$id: ${#files[@]} file(s) attached"
+}
+
 cmd_migrate() {
     init_json
     echo "Migrating issues..."
@@ -1228,7 +1267,8 @@ main() {
     init_json
     case "${1:-}" in
         list)   cmd_list;;
-        add)    cmd_add "$2" "$3" "$4" "$5";;
+        add)    shift; cmd_add "$@";;
+        attach) shift; cmd_attach "$@";;
         assign) cmd_assign "$2";;
         review) cmd_review "$2";;
         done)   cmd_done "$2";;
@@ -1236,17 +1276,27 @@ main() {
         edit)   [[ -z "$2" ]] && { echo "Usage: viban edit <id>"; exit 1; }; edit_issue "$2";;
         priority) cmd_priority "$2" "$3";;
         migrate) cmd_migrate;;
+        --version|-v)
+            # Get version from package.json
+            if [[ -f "$VIBAN_SCRIPT_DIR/package.json" ]]; then
+                grep '"version"' "$VIBAN_SCRIPT_DIR/package.json" | sed 's/.*: *"\([^"]*\)".*/\1/'
+            else
+                echo "unknown"
+            fi
+            ;;
         help|--help|-h)
             echo "viban - Vibe Kanban"
             echo ""
             echo "  viban             TUI"
             echo "  viban list        Show board"
-            echo "  viban add \"title\" [\"desc\"] [P0-P3] [type]  Add task"
+            echo "  viban add \"title\" [\"desc\"] [P0-P3] [type] [files...]  Add task"
+            echo "  viban attach <id> <file1> [file2...]  Attach files to task"
             echo "  viban priority <id> <P0-P3>   Set priority"
             echo "  viban assign      Assign first backlog (by priority)"
             echo "  viban review      → Human Review"
             echo "  viban done <id>   Complete & remove"
             echo "  viban edit <id>   Edit task in editor"
+            echo "  viban get <id>    Get task details (JSON)"
             echo "  viban migrate     Migrate: extract type from title"
             echo ""
             echo "  Priority: P0=CRITICAL, P1=HIGH, P2=MEDIUM, P3=LOW"

package/commands/task.md

@@ -95,7 +95,7 @@ Error log or stack trace
 ### Step 4: Register viban Issue
 
 ```bash
-viban add "{short_title}" "$'## Symptoms\n...(body)'" {priority} {type}
+viban add "{short_title}" "$'## Symptoms\n...(body)'" {priority} {type} [attachments...]
 ```
 
 **Parameters**:
@@ -103,6 +103,7 @@ viban add "{short_title}" "$'## Symptoms\n...(body)'" {priority} {type}
 - `description`: Issue body (Markdown)
 - `priority`: P0, P1, P2, P3 (default: P3)
 - `type`: bug, feat, chore, refactor
+- `attachments`: (optional) File paths to attach (screenshots, logs, etc.)
 
 **Examples**:
 ```bash
@@ -114,8 +115,42 @@ viban add "Dark mode support" "$'## Symptoms\n...'" P2 feat
 
 # REFACTOR issue
 viban add "Separate auth logic" "$'## Symptoms\n...'" P3 refactor
+
+# With screenshot attachments
+viban add "Layout broken on mobile" "$'## Symptoms\n...'" P1 bug ./screenshots/mobile-bug.png
+
+# With multiple attachments
+viban add "Chart rendering issue" "$'## Symptoms\n...'" P1 bug ./error.png ./console-log.txt
 ```
 
+### Step 4a: Attaching Screenshots (Recommended for Visual Issues)
+
+For visual bugs (layout issues, UI glitches, rendering problems), attaching screenshots significantly helps:
+
+1. **Take a screenshot** of the problem:
+   - macOS: `Cmd + Shift + 4` (selection) or `Cmd + Shift + 3` (full screen)
+   - Save to project directory: `./screenshots/` or `./.viban/attachments/`
+
+2. **Attach during creation**:
+   ```bash
+   viban add "Button misaligned on dashboard" "$'## Symptoms\n...'" P1 bug ./screenshots/button-issue.png
+   ```
+
+3. **Or attach to existing issue**:
+   ```bash
+   viban attach {issue_id} ./screenshots/screenshot1.png ./screenshots/screenshot2.png
+   ```
+
+4. **View attachments**:
+   ```bash
+   viban get {issue_id}
+   ```
+
+> **Why attach screenshots?**
+> - Claude Code can read image files and understand visual context
+> - The assignee can see exactly what the problem looks like
+> - Reduces back-and-forth clarification
+
 ### Step 5: Report Results
 
 After registration, report to user:
@@ -183,3 +218,31 @@ Location: src/pages/backtest/results.tsx
   viban list
   ```
 - **Accurate Priority**: P0 only for system-down level, avoid over-estimation
+
+## Final Step: Version Check & Update Prompt
+
+After completing issue registration, check for viban updates:
+
+```bash
+CURRENT_VERSION=$(viban --version 2>/dev/null || echo "unknown")
+LATEST_VERSION=$(npm show claude-plugin-viban version 2>/dev/null || echo "unknown")
+```
+
+If `CURRENT_VERSION` != `LATEST_VERSION`:
+
+```
+📦 viban update available: {CURRENT_VERSION} → {LATEST_VERSION}
+```
+
+Use AskUserQuestion to ask:
+- "Update viban now?" with options: "Yes, update" / "Skip for now"
+
+If user chooses to update:
+```bash
+npm update -g claude-plugin-viban
+```
+
+Then confirm:
+```
+✓ viban updated to {LATEST_VERSION}
+```

package/package.json

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