@su-record/vibe 2.5.7 → 2.5.8

package/skills/git-worktree.md

@@ -1,181 +1,181 @@
----
-description: Git Worktree for parallel branch work. Auto-activates for PR review, hotfix, parallel testing, or working on multiple branches simultaneously.
----
-# Git Worktree Skill
-
-Parallel branch work using Git Worktree
-
-## Overview
-
-Perform reviews/tests on other branches without interrupting main work
-
-## Usage
-
-```bash
-# Create worktree
-git worktree add ../review-pr123 pr/123
-
-# Work in that directory
-cd ../review-pr123
-npm test
-
-# Clean up after work is done
-git worktree remove ../review-pr123
-```
-
-## Commands
-
-### Create Worktree
-
-```bash
-# Worktree for PR review
-git worktree add ../review-{pr_number} origin/pr/{pr_number}
-
-# Worktree for specific branch
-git worktree add ../feature-work feature/new-feature
-
-# Worktree with new branch
-git worktree add -b hotfix/urgent ../hotfix main
-```
-
-### List Worktrees
-
-```bash
-git worktree list
-# /path/to/main       abc1234 [main]
-# /path/to/review-123 def5678 [pr/123]
-```
-
-### Remove Worktree
-
-```bash
-# Normal removal
-git worktree remove ../review-123
-
-# Force removal (ignore uncommitted changes)
-git worktree remove --force ../review-123
-
-# Prune stale worktrees
-git worktree prune
-```
-
-## Workflow Integration
-
-### PR Review Workflow
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│  /vibe.review PR#123                                             │
-├─────────────────────────────────────────────────────────────────┤
-│                                                                 │
-│  1. git worktree add ../review-123 origin/pr/123               │
-│  2. cd ../review-123                                            │
-│  3. npm install && npm test                                     │
-│  4. Run parallel review agents                                  │
-│  5. Generate review report                                      │
-│  6. cd - && git worktree remove ../review-123                  │
-│                                                                 │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-### Hotfix Workflow
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│  Urgent hotfix while working on feature                         │
-├─────────────────────────────────────────────────────────────────┤
-│                                                                 │
-│  # Keep feature work intact                                     │
-│  git worktree add -b hotfix/critical ../hotfix main            │
-│  cd ../hotfix                                                   │
-│                                                                 │
-│  # Fix and deploy                                               │
-│  vim src/bug.py                                                 │
-│  git commit -am "fix: critical bug"                             │
-│  git push origin hotfix/critical                                │
-│                                                                 │
-│  # Return to feature                                            │
-│  cd - && git worktree remove ../hotfix                         │
-│                                                                 │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-## Benefits
-
-1. **No Stash Needed**: Keep current work intact
-2. **Full Codebase**: Each worktree is a complete codebase
-3. **Parallel Work**: Work on multiple branches simultaneously
-4. **Clean Testing**: Test in isolated environment
-
-## Best Practices
-
-### Naming Convention
-
-```bash
-# PR review
-../review-{pr_number}
-
-# Hotfix
-../hotfix-{issue_number}
-
-# Experiment
-../experiment-{feature_name}
-```
-
-### Cleanup
-
-```bash
-# Regular cleanup
-git worktree prune
-
-# Check all worktrees
-git worktree list
-
-# Auto cleanup with script
-for wt in $(git worktree list --porcelain | grep worktree | cut -d' ' -f2); do
-  if [[ $wt == *"review-"* ]] || [[ $wt == *"hotfix-"* ]]; then
-    git worktree remove "$wt" 2>/dev/null || true
-  fi
-done
-```
-
-### Integration with CI/CD
-
-```yaml
-# GitHub Actions example
-- name: Setup Review Worktree
-  run: |
-    git fetch origin pull/${{ github.event.pull_request.number }}/head:pr-${{ github.event.pull_request.number }}
-    git worktree add ../review pr-${{ github.event.pull_request.number }}
-
-- name: Run Tests in Worktree
-  working-directory: ../review
-  run: npm test
-
-- name: Cleanup
-  run: git worktree remove ../review
-```
-
-## Troubleshooting
-
-### "already checked out" Error
-
-```bash
-# Solution: Branch is already in another worktree
-git worktree list  # Check
-git worktree remove <path>  # Remove
-```
-
-### Locked Worktree
-
-```bash
-# Solution: Unlock the locked worktree
-git worktree unlock <path>
-```
-
-### Stale Worktree
-
-```bash
-# Solution: Clean up deleted directories
-git worktree prune
-```
+---
+description: Git Worktree for parallel branch work. Auto-activates for PR review, hotfix, parallel testing, or working on multiple branches simultaneously.
+---
+# Git Worktree Skill
+
+Parallel branch work using Git Worktree
+
+## Overview
+
+Perform reviews/tests on other branches without interrupting main work
+
+## Usage
+
+```bash
+# Create worktree
+git worktree add ../review-pr123 pr/123
+
+# Work in that directory
+cd ../review-pr123
+npm test
+
+# Clean up after work is done
+git worktree remove ../review-pr123
+```
+
+## Commands
+
+### Create Worktree
+
+```bash
+# Worktree for PR review
+git worktree add ../review-{pr_number} origin/pr/{pr_number}
+
+# Worktree for specific branch
+git worktree add ../feature-work feature/new-feature
+
+# Worktree with new branch
+git worktree add -b hotfix/urgent ../hotfix main
+```
+
+### List Worktrees
+
+```bash
+git worktree list
+# /path/to/main       abc1234 [main]
+# /path/to/review-123 def5678 [pr/123]
+```
+
+### Remove Worktree
+
+```bash
+# Normal removal
+git worktree remove ../review-123
+
+# Force removal (ignore uncommitted changes)
+git worktree remove --force ../review-123
+
+# Prune stale worktrees
+git worktree prune
+```
+
+## Workflow Integration
+
+### PR Review Workflow
+
+```
+┌─────────────────────────────────────────────────────────────────┐
+│  /vibe.review PR#123                                             │
+├─────────────────────────────────────────────────────────────────┤
+│                                                                 │
+│  1. git worktree add ../review-123 origin/pr/123               │
+│  2. cd ../review-123                                            │
+│  3. npm install && npm test                                     │
+│  4. Run parallel review agents                                  │
+│  5. Generate review report                                      │
+│  6. cd - && git worktree remove ../review-123                  │
+│                                                                 │
+└─────────────────────────────────────────────────────────────────┘
+```
+
+### Hotfix Workflow
+
+```
+┌─────────────────────────────────────────────────────────────────┐
+│  Urgent hotfix while working on feature                         │
+├─────────────────────────────────────────────────────────────────┤
+│                                                                 │
+│  # Keep feature work intact                                     │
+│  git worktree add -b hotfix/critical ../hotfix main            │
+│  cd ../hotfix                                                   │
+│                                                                 │
+│  # Fix and deploy                                               │
+│  vim src/bug.py                                                 │
+│  git commit -am "fix: critical bug"                             │
+│  git push origin hotfix/critical                                │
+│                                                                 │
+│  # Return to feature                                            │
+│  cd - && git worktree remove ../hotfix                         │
+│                                                                 │
+└─────────────────────────────────────────────────────────────────┘
+```
+
+## Benefits
+
+1. **No Stash Needed**: Keep current work intact
+2. **Full Codebase**: Each worktree is a complete codebase
+3. **Parallel Work**: Work on multiple branches simultaneously
+4. **Clean Testing**: Test in isolated environment
+
+## Best Practices
+
+### Naming Convention
+
+```bash
+# PR review
+../review-{pr_number}
+
+# Hotfix
+../hotfix-{issue_number}
+
+# Experiment
+../experiment-{feature_name}
+```
+
+### Cleanup
+
+```bash
+# Regular cleanup
+git worktree prune
+
+# Check all worktrees
+git worktree list
+
+# Auto cleanup with script
+for wt in $(git worktree list --porcelain | grep worktree | cut -d' ' -f2); do
+  if [[ $wt == *"review-"* ]] || [[ $wt == *"hotfix-"* ]]; then
+    git worktree remove "$wt" 2>/dev/null || true
+  fi
+done
+```
+
+### Integration with CI/CD
+
+```yaml
+# GitHub Actions example
+- name: Setup Review Worktree
+  run: |
+    git fetch origin pull/${{ github.event.pull_request.number }}/head:pr-${{ github.event.pull_request.number }}
+    git worktree add ../review pr-${{ github.event.pull_request.number }}
+
+- name: Run Tests in Worktree
+  working-directory: ../review
+  run: npm test
+
+- name: Cleanup
+  run: git worktree remove ../review
+```
+
+## Troubleshooting
+
+### "already checked out" Error
+
+```bash
+# Solution: Branch is already in another worktree
+git worktree list  # Check
+git worktree remove <path>  # Remove
+```
+
+### Locked Worktree
+
+```bash
+# Solution: Unlock the locked worktree
+git worktree unlock <path>
+```
+
+### Stale Worktree
+
+```bash
+# Solution: Clean up deleted directories
+git worktree prune
+```

package/skills/parallel-research.md

@@ -1,77 +1,77 @@
----
-description: Parallel research guide. Auto-activates for complex features, new technologies, security-critical work, architecture design, or technology selection decisions.
----
-# Parallel Research
-
-Parallel research patterns for solving complex problems.
-
-## When Parallel Research is Needed
-
-| Situation | Reason |
-|-----------|--------|
-| New technology adoption | Need best practices |
-| Security-related features | Multi-angle review needed |
-| Architecture design | Multiple perspectives needed |
-| Technology selection | Comparison analysis needed |
-| Complex bugs | Explore multiple causes |
-
-## Research Agents (4 Parallel)
-
-| Agent | Role | Tools |
-|-------|------|-------|
-| best-practices | Search best practices | Web Search, context7 |
-| framework-docs | Search official docs | context7 |
-| codebase-patterns | Analyze existing code patterns | Grep, Glob |
-| security-advisory | Search security advisories | Web Search |
-
-## Usage Methods
-
-### Method 1: Direct Orchestrator Call
-
-```bash
-node -e "import('@su-record/vibe/orchestrator').then(o =>
-  o.research('passkey authentication', ['React', 'Supabase'])
-  .then(r => console.log(r.content[0].text))
-)"
-```
-
-### Method 2: Use /vibe.spec
-
-```
-/vibe.spec "feature-name"
-→ Parallel research runs automatically after requirements confirmed
-```
-
-### Method 3: Parallel Task Tool Execution
-
-```
-Task 1: "Search React auth best practices"
-Task 2: "Search Supabase Auth official docs" (concurrent)
-Task 3: "Analyze existing auth code patterns" (concurrent)
-Task 4: "Search auth security vulnerabilities" (concurrent)
-```
-
-## Using Research Results
-
-```
-Parallel research complete
-    ↓
-Synthesize results
-    ↓
-Reflect in SPEC Context section
-OR
-Reference during implementation
-```
-
-## When Research is NOT Needed
-
-- Simple CRUD operations
-- Already familiar patterns
-- Similar code exists in project
-- Time-critical (supplement with review later)
-
-## Notes
-
-- Research runs **after requirements confirmed**
-- Split overly broad topics
-- Research results are references, not absolute truth
+---
+description: Parallel research guide. Auto-activates for complex features, new technologies, security-critical work, architecture design, or technology selection decisions.
+---
+# Parallel Research
+
+Parallel research patterns for solving complex problems.
+
+## When Parallel Research is Needed
+
+| Situation | Reason |
+|-----------|--------|
+| New technology adoption | Need best practices |
+| Security-related features | Multi-angle review needed |
+| Architecture design | Multiple perspectives needed |
+| Technology selection | Comparison analysis needed |
+| Complex bugs | Explore multiple causes |
+
+## Research Agents (4 Parallel)
+
+| Agent | Role | Tools |
+|-------|------|-------|
+| best-practices | Search best practices | Web Search, context7 |
+| framework-docs | Search official docs | context7 |
+| codebase-patterns | Analyze existing code patterns | Grep, Glob |
+| security-advisory | Search security advisories | Web Search |
+
+## Usage Methods
+
+### Method 1: Direct Orchestrator Call
+
+```bash
+node -e "import('@su-record/vibe/orchestrator').then(o =>
+  o.research('passkey authentication', ['React', 'Supabase'])
+  .then(r => console.log(r.content[0].text))
+)"
+```
+
+### Method 2: Use /vibe.spec
+
+```
+/vibe.spec "feature-name"
+→ Parallel research runs automatically after requirements confirmed
+```
+
+### Method 3: Parallel Task Tool Execution
+
+```
+Task 1: "Search React auth best practices"
+Task 2: "Search Supabase Auth official docs" (concurrent)
+Task 3: "Analyze existing auth code patterns" (concurrent)
+Task 4: "Search auth security vulnerabilities" (concurrent)
+```
+
+## Using Research Results
+
+```
+Parallel research complete
+    ↓
+Synthesize results
+    ↓
+Reflect in SPEC Context section
+OR
+Reference during implementation
+```
+
+## When Research is NOT Needed
+
+- Simple CRUD operations
+- Already familiar patterns
+- Similar code exists in project
+- Time-critical (supplement with review later)
+
+## Notes
+
+- Research runs **after requirements confirmed**
+- Split overly broad topics
+- Research results are references, not absolute truth