@su-record/vibe 2.6.34 → 2.6.41

package/skills/commit-push-pr/SKILL.md

@@ -0,0 +1,118 @@
+---
+name: commit-push-pr
+description: "Commit, push, and create PR in one go. Auto-activates on commit, PR, push keywords."
+triggers: [commit, push, PR, pull request, merge]
+priority: 70
+---
+
+# Commit-Push-PR — From Commit to PR in One Step
+
+Commit current changes, push to the remote branch, and create a GitHub PR.
+
+## Pre-checks
+
+```bash
+# Check current state
+git status
+git diff --stat
+git log --oneline -5
+```
+
+## Workflow
+
+1. Review and stage changed files
+2. Write commit message (Conventional Commits format)
+3. Push to remote branch
+4. Create PR with `gh pr create`
+5. Write PR title/body
+
+## Commit Message Format
+
+```
+[type] title (under 50 chars)
+
+body (optional, 72 char line wrap)
+- What was changed
+- Why it was changed
+
+Co-Authored-By: Claude <noreply@anthropic.com>
+```
+
+### Type List
+
+| Type | Description |
+|------|-------------|
+| `feat` | New feature |
+| `fix` | Bug fix |
+| `docs` | Documentation changes |
+| `style` | Formatting (no code changes) |
+| `refactor` | Refactoring |
+| `test` | Add/modify tests |
+| `chore` | Build, config changes |
+| `perf` | Performance improvement |
+
+## Co-Authored-By Rule
+
+Always add for AI-generated/modified code:
+
+```
+Co-Authored-By: Claude <noreply@anthropic.com>
+```
+
+## Security File Check
+
+Always verify before committing:
+
+```bash
+# Detect sensitive files
+git diff --cached --name-only | grep -E '\.(env|pem|key)$|credentials|secret'
+```
+
+### Never Commit These Files
+
+| File Pattern | Reason |
+|-------------|--------|
+| `.env`, `.env.local` | Environment variables (contains secrets) |
+| `*.pem`, `*.key` | Certificates/keys |
+| `credentials.json` | Authentication info |
+| `service-account.json` | Service account |
+
+> If any of these files are staged, immediately warn and abort the commit.
+
+## Branch Protection Rules
+
+### main/master Branch Protection
+
+```bash
+# Check current branch
+git branch --show-current
+```
+
+- **No direct commits/pushes to main/master**
+- If on main/master: recommend creating a new branch and abort
+- **Never** `--force` push (main/master)
+
+## PR Creation Format
+
+```bash
+gh pr create \
+  --title "[type] title" \
+  --body "## Changes
+- Key changes
+
+## Related Issues
+- Closes #issue-number
+
+## Testing
+- Test methods and results"
+```
+
+## git-workflow Rule Integration
+
+This skill follows rules from `.claude/vibe/rules/standards/git-workflow.md`:
+
+- Conventional Commits format
+- PR checklist compliance
+- Prohibited actions (force push, .env commits, etc.)
+
+> **VIBE tool integration**: `/vibe.review`'s git-history agent automatically validates commit quality

package/skills/context7-usage/SKILL.md

@@ -0,0 +1,105 @@
+---
+name: context7-usage
+description: "Context7 plugin for latest library documentation. Auto-activates when docs, documentation, latest version, official docs, API reference, or library help is needed."
+triggers: [docs, documentation, latest version, official docs, API reference, library help, context7]
+priority: 60
+---
+
+# Context7 Usage
+
+Guide for searching latest library/framework documentation using Context7 plugin with subagent isolation.
+
+## Why Subagent Approach?
+
+| Approach | Problem |
+|----------|---------|
+| Direct plugin call | Docs content fills main context, causing bloat |
+| Subagent isolation | Docs queried in separate context, only results returned |
+
+**Benefits:**
+
+- Prevents context bloat during long coding sessions
+- Solves knowledge cutoff problem with latest docs
+- Main context stays focused on implementation
+
+## When to Use
+
+| Situation | Example |
+|-----------|---------|
+| Latest API check | "React 19 use() hook usage" |
+| Version differences | "Next.js 15 changes" |
+| Official docs needed | "Prisma schema syntax" |
+| Migration guide | "Vue 2 → Vue 3 migration" |
+
+## How It Works
+
+```
+User asks library question
+    ↓
+Skill detects docs need
+    ↓
+Spawn docs-researcher subagent (haiku)
+    ↓
+Subagent calls context7 in isolated context
+    ↓
+Returns only relevant info to main context
+```
+
+## Usage
+
+### Automatic (Recommended)
+
+Just ask library/API questions naturally:
+
+```
+"How do I use React 19 use() hook?"
+"What's new in Next.js 15?"
+"Prisma many-to-many relation syntax"
+```
+
+The skill auto-detects and spawns a docs-researcher subagent.
+
+### Manual Command
+
+```
+/context7:docs <library> [query]
+```
+
+Examples:
+
+```
+/context7:docs react hooks
+/context7:docs next.js app router
+/context7:docs prisma relations
+```
+
+## Implementation Pattern
+
+When you detect a library/API documentation need, spawn a subagent:
+
+```
+Task tool call:
+- subagent_type: Explore
+- model: haiku
+- prompt: "Use context7 to find [library] documentation about [topic]. Return only the relevant API usage examples and key points."
+```
+
+The subagent handles the context7 calls and returns a summary, keeping main context clean.
+
+## Fallback Chain
+
+```
+context7 plugin not installed
+    ↓
+Prompt user: /plugin install context7
+    ↓
+If still unavailable: Web Search for official docs
+```
+
+## Installation
+
+If context7 is not installed, guide user:
+
+```bash
+/plugin install context7
+```

package/skills/core-capabilities/SKILL.md

@@ -0,0 +1,164 @@
+---
+name: core-capabilities
+description: "Core framework capabilities overview. Auto-activates when working on core projects, asking about available features, or needing workflow guidance."
+triggers: [core, capabilities, features, workflow, framework guide]
+priority: 50
+---
+# Core Capabilities
+
+Complete guide to core's scenario-driven development framework.
+
+## Core Workflow
+
+```
+/vibe.spec → /vibe.run → /vibe.verify → /vibe.review
+```
+
+## Slash Commands
+
+| Command | Purpose |
+|---------|---------|
+| `/vibe.spec "feature"` | Create SPEC with PTCF structure + 8 parallel research |
+| `/vibe.spec "feature" split` | Create multiple SPECs for large scope features |
+| `/vibe.run "feature"` | Implement based on SPEC |
+| `/vibe.run "feature" ultrawork` | Maximum performance mode |
+| `/vibe.verify "feature"` | BDD scenario verification |
+| `/vibe.review` | Parallel code review (13+ agents) |
+| `/vibe.analyze` | Project analysis |
+| `/vibe.reason "problem"` | Systematic reasoning |
+| `/vibe.utils --e2e` | Playwright E2E testing |
+| `/vibe.utils --diagram` | Generate diagrams |
+| `/vibe.utils --ui "description"` | UI preview |
+| `/vibe.utils --continue` | Session restore (load previous context) |
+| `/vibe.utils --compound` | Document solutions |
+
+## Built-in Tools
+
+### Semantic Code Analysis
+
+```bash
+node -e "import('@su-record/vibe/tools').then(t => t.TOOL_NAME({...}))"
+```
+
+| Tool | Purpose |
+|------|---------|
+| `findSymbol` | Find symbol definitions |
+| `findReferences` | Find all references |
+| `analyzeComplexity` | Code complexity analysis |
+| `validateCodeQuality` | Quality validation |
+
+### Memory Management
+
+| Tool | Purpose |
+|------|---------|
+| `startSession` | Start session (restore previous context) |
+| `autoSaveContext` | Save current state |
+| `saveMemory` | Save important decisions |
+| `recallMemory` | Recall saved memory |
+| `listMemories` | List saved memories |
+
+## Orchestrator
+
+### Background Agents
+
+```bash
+node -e "import('@su-record/vibe/orchestrator').then(o =>
+  o.launchBackgroundAgent({ prompt: '...', agentName: '...' })
+)"
+```
+
+## Multi-LLM Research (v2.5.0)
+
+GPT/Gemini are automatically called within `/vibe.spec`:
+
+```text
+/vibe.spec "feature"
+      ↓
+[Claude] Draft SPEC
+      ↓
+[Parallel Research] 8 parallel tasks:
+  - 4x Bash: GPT/Gemini (best practices + security)
+  - 4x Task: Claude agents (docs, patterns, advisories)
+      ↓
+[SPEC Review] GPT + Gemini parallel review
+      ↓
+[Claude] Finalize SPEC
+```
+
+| Phase | Method | Tasks |
+|-------|--------|-------- |
+| Research | `llm-orchestrate.js` via Bash | GPT best practices, GPT security, Gemini best practices, Gemini security |
+| Research | Task tool (Claude agents) | framework-docs, codebase-patterns, best-practices, security-advisory |
+| SPEC Review | `llm-orchestrate.js` via Bash | SPEC quality validation |
+| Docs | context7 MCP | Latest library documentation |
+
+**Setup:**
+```bash
+vibe gpt auth       # Enable GPT
+vibe gemini auth    # Enable Gemini
+vibe status         # Check current settings
+```
+
+## ULTRAWORK Mode
+
+Add `ultrawork` or `ulw` for maximum performance:
+
+- Parallel subagent exploration (3+ concurrent)
+- Background agents preparing next phase
+- Phase pipelining (no wait between phases)
+- Boulder Loop (auto-progress until complete)
+- Auto-retry on errors (max 3 times)
+- Auto-compress at 70%+ context
+
+## Review Agents (13+)
+
+| Category | Agents |
+|----------|--------|
+| Security | security-reviewer, data-integrity-reviewer |
+| Performance | performance-reviewer, complexity-reviewer |
+| Architecture | architecture-reviewer, simplicity-reviewer |
+| Language | python, typescript, rails, react reviewers |
+| Context | git-history, test-coverage reviewers |
+
+## Project Structure
+
+```
+# Global (~/.claude/)
+~/.claude/
+├── commands/          # Slash commands
+├── agents/            # Sub-agents
+├── skills/            # Auto-activated guides
+└── core/
+    ├── rules/         # Coding rules
+    ├── languages/     # Language guides
+    └── templates/     # Templates
+
+# Global (%APPDATA%/core/ or ~/.config/vibe/)
+core/
+├── hooks/scripts/     # Hook scripts (llm-orchestrate.js)
+├── gpt.json           # GPT credentials
+└── gemini.json        # Gemini credentials
+
+# Project (.claude/)
+.claude/
+├── settings.local.json  # Hooks config (personal, gitignored)
+└── core/
+    ├── specs/           # SPEC documents
+    ├── features/        # BDD scenarios
+    ├── config.json      # Project config
+    └── constitution.md  # Project rules
+```
+
+## Context Management
+
+- Session start: Auto-restore previous context
+- 70/80/90%: Auto-save checkpoints
+- Context overflow: Use `saveMemory` → `/new`
+
+## Without Commands
+
+Even without `/vibe.*` commands, you can:
+
+1. Call tools directly via node commands
+2. Reference skills for guidance
+3. Apply coding rules from `~/.claude/vibe/rules/` (global)

package/skills/git-worktree/SKILL.md

@@ -0,0 +1,184 @@
+---
+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
+```

package/skills/handoff/SKILL.md

@@ -0,0 +1,101 @@
+---
+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`.