@su-record/vibe 2.0.11 → 2.2.1

package/.claude/commands/vibe.reason.md

@@ -1,306 +0,0 @@
----
-description: Apply systematic reasoning framework to complex problems
-argument-hint: "problem description"
----
-
-# /vibe.reason
-
-Apply 9-step reasoning framework to complex problems (Reasoning Agent).
-
-## Usage
-
-```
-/vibe.reason "problem description"
-```
-
-## Description
-
-Use systematic 9-step reasoning framework to logically analyze complex problems and derive optimal solutions.
-
-## When to Use
-
-Use in situations like:
-
-1. **Complex bug debugging**
-   - Root cause unclear
-   - Need to systematically verify multiple hypotheses
-
-2. **Architecture design decisions**
-   - Need to choose optimal option among several
-   - Need to comprehensively evaluate constraints and risks
-
-3. **Performance optimization**
-   - Bottleneck may be in multiple places
-   - Need step-by-step optimization strategy
-
-4. **Refactoring planning**
-   - Need to systematically analyze legacy code complexity
-   - Need gradual refactoring strategy
-
-5. **Requirements analysis**
-   - Need to reconcile conflicting requirements
-   - Need to discover missing requirements
-
-## Process
-
-### 1. Logical Dependencies and Constraints
-- Check policies, rules, prerequisites
-- Optimize task order (identify dependencies)
-- Apply user constraints first
-
-### 2. Risk Assessment
-- Analyze action consequences
-- Check rollback possibility
-- Review compatibility, security, performance risks
-
-### 3. Inductive Reasoning and Hypothesis Exploration
-- Generate hypotheses about root cause
-- Prioritize by likelihood
-- Present verification method for each hypothesis
-
-### 4. Result Evaluation and Adaptability
-- Modify plan based on observations
-- Generate new hypothesis when disproved
-- Determine backtracking need
-
-### 5. Information Availability
-- Identify all available tools
-- Reference relevant policy/rule documents
-- Restore previous context
-- Distinguish items needing user confirmation
-
-### 6. Precision and Evidence
-- Cite exact source when referencing policies
-- Include filename:line when referencing code
-- Provide exact metric numbers
-
-### 7. Completeness
-- Integrate all requirements, options, preferences
-- Avoid premature conclusions
-- Explore multiple alternatives
-
-### 8. Persistence and Patience
-- Intelligently retry temporary errors
-- Solve problems through strategy changes
-- Continue until all reasoning steps complete
-
-### 9. Response Suppression
-- Act only after reasoning complete
-- Document reasoning process for complex decisions
-- Ensure safety through step-by-step execution
-
-## MCP Tools Integration
-
-This command automatically uses these MCP tools:
-
-- **apply_reasoning_framework**: Apply 9-step reasoning framework
-- **create_thinking_chain**: Create sequential thinking chain
-- **analyze_problem**: Analyze problem root cause
-- **step_by_step_analysis**: Detailed step-by-step analysis
-- **recall_memory**: Restore previous context
-- **find_symbol / find_references**: Identify code dependencies
-
-## Output Format
-
-```markdown
-# Reasoning Framework Analysis
-
-**Problem**: [problem description]
-**Context**: [relevant information]
-**Steps Applied**: 9/9
-
----
-
-## 1. Logical Dependencies and Constraints
-
-**Key Questions**:
-- What policies or required rules apply?
-- Should task order be rearranged?
-- Required prerequisites or information?
-- Explicit user constraints?
-
-**Constraint Analysis**:
-[analysis content]
-
----
-
-## 2. Risk Assessment
-
-...
-
----
-
-## Summary
-
-[Overall reasoning results summary and recommendations]
-```
-
-## Examples
-
-### Example 1: Complex Bug Debugging
-
-```
-User: /vibe.reason "After user login, profile page intermittently returns 500 error. Log shows 'TypeError: Cannot read property id of undefined'"
-
-AI: Analyzing this problem with 9-step reasoning framework.
-
-# Reasoning Framework Analysis
-
-**Problem**: Intermittent 500 error on profile page after login (TypeError: Cannot read property 'id' of undefined)
-**Context**: Intermittent occurrence, happens after successful login
-**Steps Applied**: 9/9
-
----
-
-## 1. Logical Dependencies and Constraints
-
-**Constraint Analysis**:
-- Policy/Rules: Need to check auth/authz system policies
-- Task Order: Verify login → session creation → profile fetch order
-- Prerequisites: Need to identify error reproduction conditions
-- User Constraints: Production environment limits debugging tools
-
----
-
-## 2. Risk Assessment
-
-**Risk Assessment**:
-- Task type: Debugging (medium risk - logging low risk, DB changes high risk)
-- Rollback possibility: Adding logs easy to rollback
-- Compatibility risk: Session structure changes affect existing users
-- Security risk: Excessive logging may expose sensitive info
-- Performance risk: Additional logging minimal impact
-
----
-
-## 3. Inductive Reasoning and Hypothesis Exploration
-
-**Hypothesis Generation**:
-1. **Hypothesis 1: Incomplete session data** (Likelihood: High)
-   - Evidence: Intermittent = timing issue or data consistency problem
-   - Verification: Add logging to session save logic, check Redis connection
-
-2. **Hypothesis 2: Async processing order issue** (Likelihood: Medium)
-   - Evidence: undefined = accessing data before load
-   - Verification: Check Promise chain in profile API, check for missing await
-
-3. **Hypothesis 3: DB query returns null** (Likelihood: Low)
-   - Evidence: User info fetch fails only under certain conditions
-   - Verification: Check profile query logs, review foreign key constraints
-
-**Priority**: Verify in order of likelihood, don't completely rule out low probability
-
----
-
-[Additional steps 4-9 analysis...]
-
----
-
-## Summary
-
-Analyzed profile page 500 error after login through 9-step reasoning framework.
-
-**Key Findings**:
-- Most likely cause: Incomplete session data (Redis connection issue or session save timing)
-- Verification priority: 1) Add session save logic logging → 2) Review async processing → 3) Check DB queries
-
-**Recommended Actions**:
-1. Immediate: Add detailed logging to session save/fetch (low risk)
-2. Short-term: Code review async processing (Promise, await check)
-3. Medium-term: Strengthen session store monitoring (Redis connection, memory)
-
-**Next Steps**:
-Check `profile_controller.ts` → Add try-catch and logging to session processing logic → Identify reproduction conditions
-```
-
-### Example 2: Architecture Design Decision
-
-```
-User: /vibe.reason "Want to add real-time notification feature. Should I use WebSocket, SSE, or Long Polling?"
-
-AI: [Systematically analyze constraints, risks, pros/cons of each option through 9-step framework, recommend optimal choice for project situation]
-```
-
-## Integration with Other Commands
-
-### With /vibe.spec
-
-```
-# 1. Collect requirements
-/vibe.spec "real-time notifications"
-
-# 2. When technical decision needed
-/vibe.reason "Choosing WebSocket vs SSE vs Long Polling for real-time notifications"
-
-# 3. Update SPEC document and create plan
-/vibe.plan "real-time notifications"
-```
-
-### With /vibe.analyze
-
-```
-# 1. Discover issue through code analysis
-/vibe.analyze --code
-
-# 2. Analyze discovered issue with reasoning framework
-/vibe.reason "Refactoring strategy to reduce users_service.py Cyclomatic Complexity from 15 to under 10"
-
-# 3. Execute refactoring
-/vibe.run "Task: Refactor users_service.py"
-```
-
-## Agent Configuration
-
-This command uses `~/.claude/agents/reasoning-agent.md`.
-
-**Agent Role**:
-- Systematic reasoning and problem-solving expert
-- Logically analyze complex problems
-- Derive optimal solutions considering all relevant factors
-
-**Agent Features**:
-- Apply 9-step reasoning framework
-- Hypothesis-based approach
-- Risk assessment and mitigation strategies
-- Precise evidence and source citation
-
-## Best Practices
-
-1. **Describe problem specifically**
-   - ❌ "There's a bug"
-   - ✅ "After login, profile page intermittently returns 500 error. Error log: TypeError: Cannot read property 'id' of undefined"
-
-2. **Include context**
-   - Occurrence conditions (always? intermittent? specific conditions only?)
-   - Relevant tech stack
-   - Solutions already tried
-
-3. **Save reasoning results to memory**
-   - For complex problems, save reasoning results with `save_memory`
-   - Reference later with `recall_memory`
-
-4. **Verify step by step**
-   - Verify hypotheses suggested by reasoning framework in order
-   - Feedback each verification result to agent
-
-5. **Combine with other commands**
-   - `/vibe.analyze` to understand situation → `/vibe.reason` to analyze solution → `/vibe.run` to execute
-
-## Notes
-
-- This command is specialized for complex problems. For simple tasks, direct requests are more efficient.
-- Reasoning process may take time; allow sufficient time.
-- Reasoning results are recommendations; final decision is user's.
-- Automatically uses MCP tools, so hi-ai server must be connected.
-
-## Related
-
-- [Reasoning Agent Guide](~/.claude/agents/reasoning-agent.md)
-- [MCP hi-ai Guide](~/.claude/skills/tools/mcp-hi-ai-guide.md)
-- [/vibe.analyze](vibe.analyze.md)
-- [/vibe.spec](vibe.spec.md)
-- [/vibe.plan](vibe.plan.md)
-
----
-
-ARGUMENTS: $ARGUMENTS

package/.claude/commands/vibe.review.md

@@ -1,324 +0,0 @@
----
-description: Multi-agent parallel code review with priority-based findings
-argument-hint: "PR number, branch name, or file path"
----
-
-# /vibe.review
-
-**Parallel Agent Code Review** - 13+ specialists review simultaneously
-
-## Usage
-
-```
-/vibe.review                    # Review current branch
-/vibe.review PR#123             # Review specific PR
-/vibe.review feature/login      # Review specific branch
-/vibe.review src/api/           # Review specific path
-```
-
-## Core Principle
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│  All experts review simultaneously = Fast & Thorough            │
-│                                                                 │
-│  🔴 P1 (Critical): Blocks merge - MUST fix                      │
-│  🟡 P2 (Important): Should fix - Before merge                   │
-│  🔵 P3 (Nice-to-have): Enhancement - When time permits          │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-## Process
-
-### Phase 1: Tech Stack Detection & Target Analysis
-
-**Detect project tech stack FIRST before launching reviewers:**
-
-```
-📋 Tech Stack Detection
-├── Read package.json      → TypeScript, React, Node.js
-├── Read pyproject.toml    → Python, FastAPI, Django
-├── Read Gemfile           → Ruby, Rails
-├── Read pubspec.yaml      → Flutter, Dart
-├── Read go.mod            → Go
-├── Read CLAUDE.md         → Explicit tech stack declaration
-└── Analyze file extensions in changed files
-```
-
-**Detection Logic:**
-```javascript
-// Stack detection from project files
-const stack = {
-  typescript: hasFile("package.json") && (hasDep("typescript") || hasFile("tsconfig.json")),
-  react: hasDep("react") || hasDep("next"),
-  python: hasFile("pyproject.toml") || hasFile("requirements.txt"),
-  rails: hasFile("Gemfile") && hasDep("rails"),
-  go: hasFile("go.mod"),
-  flutter: hasFile("pubspec.yaml")
-};
-```
-
-**Changed Files Analysis:**
-```
-git diff --name-only HEAD~1
-├── src/components/*.tsx  → React reviewer needed
-├── app/api/*.py          → Python reviewer needed
-├── app/models/*.rb       → Rails reviewer needed
-└── No .ts files          → Skip TypeScript reviewer
-```
-
-### Phase 2: Parallel Agent Review (STACK-AWARE)
-
-**Launch ONLY relevant agents based on detected stack!**
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│  🚀 PARALLEL AGENT LAUNCH (Stack-Aware Selection)               │
-├─────────────────────────────────────────────────────────────────┤
-│                                                                 │
-│  ✅ ALWAYS RUN (Core Reviewers)                                 │
-│  ├── security-reviewer      # OWASP Top 10, vulnerabilities     │
-│  ├── data-integrity-reviewer # Data validation, constraints     │
-│  ├── performance-reviewer   # N+1 queries, memory leaks         │
-│  ├── architecture-reviewer  # Layer violations, cycles          │
-│  ├── complexity-reviewer    # Cyclomatic complexity, length     │
-│  ├── simplicity-reviewer    # Over-abstraction, dead code       │
-│  ├── git-history-reviewer   # Churn files, risk patterns        │
-│  └── test-coverage-reviewer # Missing tests, edge cases         │
-│                                                                 │
-│  🔍 CONDITIONAL (Based on Detected Stack)                       │
-│  ├── python-reviewer        # IF: .py files in diff             │
-│  ├── typescript-reviewer    # IF: .ts/.tsx files OR tsconfig    │
-│  ├── rails-reviewer         # IF: Gemfile has rails             │
-│  └── react-reviewer         # IF: package.json has react        │
-│                                                                 │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-**Stack-Aware Agent Invocation:**
-```javascript
-// Core reviewers (ALWAYS)
-const coreAgents = [
-  "security-reviewer",
-  "data-integrity-reviewer",
-  "performance-reviewer",
-  "architecture-reviewer",
-  "complexity-reviewer",
-  "simplicity-reviewer",
-  "git-history-reviewer",
-  "test-coverage-reviewer"
-];
-
-// Language reviewers (CONDITIONAL)
-const languageAgents = [];
-if (stack.python || changedFiles.some(f => f.endsWith('.py'))) {
-  languageAgents.push("python-reviewer");
-}
-if (stack.typescript || changedFiles.some(f => f.match(/\.tsx?$/))) {
-  languageAgents.push("typescript-reviewer");
-}
-if (stack.react) {
-  languageAgents.push("react-reviewer");
-}
-if (stack.rails) {
-  languageAgents.push("rails-reviewer");
-}
-
-// Launch ALL selected agents in parallel
-const allAgents = [...coreAgents, ...languageAgents];
-```
-
-**Example Output:**
-```
-📦 Detected Stack: TypeScript + React + Node.js
-📄 Changed Files: 12 (.tsx: 8, .ts: 3, .json: 1)
-
-🚀 Launching 10 agents (8 core + 2 language-specific):
-   ✅ security-reviewer
-   ✅ data-integrity-reviewer
-   ✅ performance-reviewer
-   ✅ architecture-reviewer
-   ✅ complexity-reviewer
-   ✅ simplicity-reviewer
-   ✅ git-history-reviewer
-   ✅ test-coverage-reviewer
-   ✅ typescript-reviewer  ← Detected: tsconfig.json
-   ✅ react-reviewer       ← Detected: react in package.json
-   ⏭️ python-reviewer      ← Skipped: No Python files
-   ⏭️ rails-reviewer       ← Skipped: No Gemfile
-```
-
-### Phase 3: Ultra-Thinking Deep Analysis
-
-Deep analysis after agent results:
-
-```markdown
-## Deep Analysis Dimensions
-
-1. **System Context**
-   - Component interactions
-   - Data flow
-   - External dependencies
-
-2. **Stakeholder Perspectives**
-   - Developers: Maintainability
-   - Ops: Deployment risk
-   - Security: Vulnerabilities
-   - Business: Impact
-
-3. **Edge Cases & Failure Scenarios**
-   - Race conditions
-   - Resource exhaustion
-   - Network failures
-   - Malicious input
-
-4. **Multiple Angles**
-   - Technical excellence
-   - Business value
-   - Risk management
-   - Team dynamics
-```
-
-### Phase 4: Findings Synthesis
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│  📊 REVIEW FINDINGS                                              │
-├─────────────────────────────────────────────────────────────────┤
-│                                                                 │
-│  🔴 P1 CRITICAL (Blocks Merge) - 2 issues                       │
-│  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━   │
-│  1. [SECURITY] SQL Injection in user query                      │
-│     📍 src/api/users.py:42                                      │
-│     💡 Use parameterized queries                                │
-│                                                                 │
-│  2. [DATA] Missing transaction rollback                         │
-│     📍 src/services/payment.py:128                              │
-│     💡 Wrap in try/except with rollback                         │
-│                                                                 │
-│  🟡 P2 IMPORTANT (Should Fix) - 5 issues                        │
-│  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━   │
-│  3. [PERF] N+1 query in user list                               │
-│  4. [ARCH] Circular dependency detected                         │
-│  5. [TEST] Missing edge case tests                              │
-│  ...                                                            │
-│                                                                 │
-│  🔵 P3 NICE-TO-HAVE (Enhancement) - 3 issues                    │
-│  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━   │
-│  8. [STYLE] Consider extracting helper function                 │
-│  ...                                                            │
-│                                                                 │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-### Phase 5: Todo File Creation
-
-Save findings to `.vibe/todos/`:
-
-```markdown
-## File Naming Convention
-
-{priority}-{category}-{short-desc}.md
-
-Examples:
-- P1-security-sql-injection.md
-- P2-perf-n1-query.md
-- P3-style-extract-helper.md
-```
-
-**Todo File Format:**
-```markdown
-# [P1] SQL Injection Vulnerability
-
-## Summary
-User input directly concatenated in SQL query
-
-## Location
-- File: src/api/users.py
-- Line: 42
-- Function: get_user_by_email()
-
-## Current Code
-```python
-query = f"SELECT * FROM users WHERE email = '{email}'"
-```
-
-## Suggested Fix
-```python
-query = "SELECT * FROM users WHERE email = %s"
-cursor.execute(query, (email,))
-```
-
-## References
-- OWASP SQL Injection: https://owasp.org/...
-- Project DB Guide: docs/database.md
-
-## Status
-- [ ] Fix implemented
-- [ ] Tests added
-- [ ] Review approved
-```
-
-### Phase 6: Optional E2E Testing
-
-```
-Suggest E2E tests based on project type:
-├── Web: /vibe.e2e (Playwright)
-├── iOS: Xcode Test
-├── Android: Espresso
-└── API: Contract Test
-```
-
-## Output
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│  📊 CODE REVIEW SUMMARY                                          │
-│  PR #123: Add user authentication                                │
-├─────────────────────────────────────────────────────────────────┤
-│                                                                 │
-│  Reviewers: 13 agents | Duration: 45s                           │
-│                                                                 │
-│  📈 Score: 72/100 (Needs Work)                                  │
-│                                                                 │
-│  Issues Found:                                                  │
-│  ├── 🔴 P1 Critical: 2 (BLOCKS MERGE)                           │
-│  ├── 🟡 P2 Important: 5                                         │
-│  └── 🔵 P3 Nice-to-have: 3                                      │
-│                                                                 │
-│  By Category:                                                   │
-│  ├── Security: 2                                                │
-│  ├── Performance: 3                                             │
-│  ├── Architecture: 1                                            │
-│  ├── Testing: 2                                                 │
-│  └── Style: 2                                                   │
-│                                                                 │
-│  📁 Todos created: .vibe/todos/ (10 files)                      │
-│                                                                 │
-│  ❌ MERGE BLOCKED - Fix P1 issues first                         │
-│                                                                 │
-│  Next Steps:                                                    │
-│  1. Fix P1-security-sql-injection.md                            │
-│  2. Fix P1-data-transaction-rollback.md                         │
-│  3. Re-run: /vibe.review                                        │
-│                                                                 │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-## Priority Guidelines
-
-| Priority | Criteria | Action |
-|----------|----------|--------|
-| 🔴 P1 | Security vulnerabilities, data loss, crashes | Block merge, fix immediately |
-| 🟡 P2 | Performance issues, architecture violations, missing tests | Fix before merge |
-| 🔵 P3 | Style, refactoring suggestions, documentation | Add to backlog |
-
-## Related Commands
-
-- `/vibe.e2e` - Run E2E tests
-- `/vibe.compound` - Document solutions
-- `/vibe.verify` - SPEC-based verification
-
----
-
-ARGUMENTS: $ARGUMENTS