@su-record/vibe 2.7.8 → 2.7.10

package/skills/git-worktree/SKILL.md

@@ -1,184 +1,72 @@
----
-name: git-worktree
-description: "Git Worktree for parallel branch work. Auto-activates for PR review, hotfix, parallel testing, or working on multiple branches simultaneously."
-triggers: [worktree, PR review, hotfix, parallel branch, multiple branches]
-priority: 50
----
-# 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
-```
+---
+name: git-worktree
+description: "Git Worktree for parallel branch work. Auto-activates for PR review, hotfix, parallel testing, or working on multiple branches simultaneously."
+triggers: [worktree, PR review, hotfix, parallel branch, multiple branches]
+priority: 50
+---
+
+# Git Worktree
+
+## Pre-check (K1)
+
+> Do you need to work on another branch without losing current work? If you can just `git stash` and switch, worktree may be overkill.
+
+## Core Commands
+
+```bash
+# Create worktree for PR review
+git worktree add ../review-{pr_number} origin/pr/{pr_number}
+
+# Create worktree with new branch (hotfix)
+git worktree add -b hotfix/urgent ../hotfix main
+
+# List all worktrees
+git worktree list
+
+# Remove when done
+git worktree remove ../review-{pr_number}
+
+# Clean up stale entries
+git worktree prune
+```
+
+## PR Review Workflow
+
+```
+1. git worktree add ../review-123 origin/pr/123
+2. cd ../review-123
+3. npm install && npm test
+4. Run review agents
+5. cd - && git worktree remove ../review-123
+```
+
+## Hotfix Workflow
+
+```
+1. git worktree add -b hotfix/critical ../hotfix main
+2. cd ../hotfix
+3. Fix bug → commit → push
+4. cd - && git worktree remove ../hotfix
+```
+
+## Naming Convention
+
+```bash
+../review-{pr_number}         # PR review
+../hotfix-{issue_number}      # Hotfix
+../experiment-{feature_name}  # Experiment
+```
+
+## Troubleshooting
+
+| Error | Fix |
+|-------|-----|
+| "already checked out" | Branch is in another worktree — `git worktree list`, then remove |
+| Locked worktree | `git worktree unlock <path>` |
+| Stale worktree | `git worktree prune` |
+
+## Done Criteria (K4)
+
+- [ ] Worktree created and work completed in isolation
+- [ ] Worktree removed after work is done
+- [ ] No stale worktrees left (`git worktree list` clean)

package/skills/handoff/SKILL.md

@@ -1,101 +1,109 @@
----
-name: handoff
-description: "Generate HANDOFF.md work handover document before session end. Auto-activates on handoff, handover, session cleanup keywords."
-triggers: [handoff, handover, session cleanup, session end, context save]
-priority: 70
----
-
-# Handoff — Session Handover Document
-
-Record work status before session end so the next session can pick up immediately.
-
-## What is HANDOFF.md?
-
-A file that records the current work status before context reset. Reading this file in a new session allows immediate continuation.
-
-### Difference from `/vibe.utils --continue`
-
-| Item | `/vibe.utils --continue` | Handoff |
-|------|--------------------------|---------|
-| Method | Automatic session context restore | Manual handover document |
-| Includes | Memory + session state | Work progress + notes + file list |
-| When to use | At new session start | Before session end |
-| Purpose | Quick auto-restore | Detailed handover (team/future self) |
-
-## When to Use
-
-- When context reaches 80-100k tokens
-- After using `/compact` 3 times
-- Before pausing work for an extended period
-- When progress recording is needed during complex work
-
-## VIBE Tool Integration
-
-Use VIBE built-in tools to save current state before generating Handoff:
-
-```bash
-# Save current session context
-core_auto_save_context
-
-# Save important decisions to memory
-core_save_memory --key "handoff-decision" --value "Decided on JWT for auth" --category "project"
-
-# Verify saved memories
-core_list_memories --category "project"
-```
-
-## HANDOFF.md Template
-
-```markdown
-# Work Handover Document
-
-## Completed Tasks
-- [x] Completed task 1
-- [x] Completed task 2
-
-## In Progress
-- [ ] Currently working on
-  - Progress: 70%
-  - Next step: implement ~~
-
-## Next Tasks
-1. High priority task
-2. Next task
-
-## Notes & Cautions
-- Do not touch: ~~
-- Known bugs: ~~
-- Temporary workarounds: ~~
-
-## Related Files
-- src/components/Login.tsx — Login form
-- src/api/auth.ts — Auth API
-
-## Last State
-- Branch: feature/auth
-- Last commit: abc1234
-- Test status: passing
-```
-
-## Generation Steps
-
-1. Check current changed files with `git status`
-2. Check recent commits with `git log --oneline -5`
-3. Organize in-progress and remaining tasks
-4. Save session context with `core_auto_save_context`
-5. Save key decisions with `core_save_memory`
-6. Generate HANDOFF.md file
-
-## Restoring in New Session
-
-```
-Read HANDOFF.md and continue working
-```
-
-Or use alongside VIBE auto-restore:
-
-```
-/vibe.utils --continue
-```
-
-In this case, saved decisions are also restored via `core_recall_memory`.
+---
+name: handoff
+description: "Generate HANDOFF.md work handover document before session end. Auto-activates on handoff, handover, session cleanup keywords."
+triggers: [handoff, handover, session cleanup, session end, context save]
+priority: 70
+---
+
+# Handoff — Session Handover Document
+
+Record work status before session end so the next session can pick up immediately.
+
+## What is HANDOFF.md?
+
+A file that records the current work status before context reset. Reading this file in a new session allows immediate continuation.
+
+### Difference from `/vibe.utils --continue`
+
+| Item | `/vibe.utils --continue` | Handoff |
+|------|--------------------------|---------|
+| Method | Automatic session context restore | Manual handover document |
+| Includes | Memory + session state | Work progress + notes + file list |
+| When to use | At new session start | Before session end |
+| Purpose | Quick auto-restore | Detailed handover (team/future self) |
+
+## When to Use
+
+- When context reaches 80-100k tokens
+- After using `/compact` 3 times
+- Before pausing work for an extended period
+- When progress recording is needed during complex work
+
+## VIBE Tool Integration
+
+Use VIBE built-in tools to save current state before generating Handoff:
+
+```bash
+# Save current session context
+core_auto_save_context
+
+# Save important decisions to memory
+core_save_memory --key "handoff-decision" --value "Decided on JWT for auth" --category "project"
+
+# Verify saved memories
+core_list_memories --category "project"
+```
+
+## HANDOFF.md Template
+
+```markdown
+# Work Handover Document
+
+## Completed Tasks
+- [x] Completed task 1
+- [x] Completed task 2
+
+## In Progress
+- [ ] Currently working on
+  - Progress: 70%
+  - Next step: implement ~~
+
+## Next Tasks
+1. High priority task
+2. Next task
+
+## Notes & Cautions
+- Do not touch: ~~
+- Known bugs: ~~
+- Temporary workarounds: ~~
+
+## Related Files
+- src/components/Login.tsx — Login form
+- src/api/auth.ts — Auth API
+
+## Last State
+- Branch: feature/auth
+- Last commit: abc1234
+- Test status: passing
+```
+
+## Generation Steps
+
+1. Check current changed files with `git status`
+2. Check recent commits with `git log --oneline -5`
+3. Organize in-progress and remaining tasks
+4. Save session context with `core_auto_save_context`
+5. Save key decisions with `core_save_memory`
+6. Generate HANDOFF.md file
+
+## Restoring in New Session
+
+```
+Read HANDOFF.md and continue working
+```
+
+Or use alongside VIBE auto-restore:
+
+```
+/vibe.utils --continue
+```
+
+In this case, saved decisions are also restored via `core_recall_memory`.
+
+## Done Criteria (K4)
+
+- [ ] HANDOFF.md created with all sections filled
+- [ ] Completed/in-progress/next tasks accurately listed
+- [ ] Related files section includes all modified files
+- [ ] Session context saved via `core_auto_save_context`
+- [ ] Key decisions saved via `core_save_memory`

package/skills/parallel-research/SKILL.md

@@ -1,80 +1,87 @@
----
-name: parallel-research
-description: "Parallel research guide. Auto-activates for complex features, new technologies, security-critical work, architecture design, or technology selection decisions."
-triggers: [parallel research, complex feature, technology selection, architecture design, security critical]
-priority: 60
----
-# 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('{{VIBE_PATH_URL}}/node_modules/@su-record/vibe/dist/infra/orchestrator/index.js').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
+---
+name: parallel-research
+description: "Parallel research guide. Auto-activates for complex features, new technologies, security-critical work, architecture design, or technology selection decisions."
+triggers: [parallel research, complex feature, technology selection, architecture design, security critical]
+priority: 60
+---
+# 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('{{VIBE_PATH_URL}}/node_modules/@su-record/vibe/dist/infra/orchestrator/index.js').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
+
+## Done Criteria (K4)
+
+- [ ] All 4 research agents returned results (or documented why not)
+- [ ] Results synthesized into actionable recommendations
+- [ ] Key findings reflected in SPEC Context section or implementation notes
+- [ ] Conflicting recommendations resolved with reasoning