@su-record/vibe 2.0.11 → 2.2.1

package/.claude/commands/vibe.analyze.md

@@ -1,239 +0,0 @@
----
-description: Analyze project or specific feature/module
-argument-hint: "feature-name" or --code or --deps or --arch (optional)
----
-
-# /vibe.analyze
-
-Analyze project or specific feature/module.
-
-## Usage
-
-```
-/vibe.analyze                  # Full project quality analysis
-/vibe.analyze "login"          # Login related code exploration + context collection
-/vibe.analyze --code           # Code quality analysis only
-/vibe.analyze --deps           # Dependency analysis only
-/vibe.analyze --arch           # Architecture analysis only
-```
-
-## ⚠️ Context Reset
-
-**When this command runs, previous conversation is ignored.**
-- Explore and analyze code from scratch like new session
-- Base conversation only on newly collected information from this analysis
-
----
-
-## Mode 1: Feature/Module Analysis (`/vibe.analyze "feature-name"`)
-
-### Goal
-
-**Explore all source code** related to user's requested feature/module and **analyze flow** to:
-1. Understand current implementation status
-2. Understand code structure and dependencies
-3. Build context for immediate response to future development/modification requests
-
-### Process
-
-#### 1. Request Analysis
-
-Extract key keywords from user request:
-- Feature name (e.g., login, feed, payment)
-- Action (e.g., create, read, update, delete)
-- Scope (e.g., backend only, frontend only, full)
-
-#### 2. Understand Project Structure
-
-Read `CLAUDE.md`, `package.json`, `pyproject.toml`, etc. to identify tech stack:
-
-**Backend:**
-- FastAPI/Django: `app/api/`, `app/services/`, `app/models/`
-- Express/NestJS: `src/controllers/`, `src/services/`, `src/models/`
-
-**Frontend:**
-- React/Next.js: `src/components/`, `src/pages/`, `src/hooks/`
-- Flutter: `lib/screens/`, `lib/services/`, `lib/providers/`
-
-#### 3. Explore Related Code
-
-**Exploration strategy:**
-1. **Glob** to collect related file list
-2. **Grep** to locate code by keyword
-3. **Read** to analyze key files in detail
-4. If needed, **Task (Explore)** agent for parallel exploration
-
-#### 4. Flow Analysis
-
-**API Flow:**
-- Endpoint URL and HTTP method
-- Request/response schema
-- Authentication/authorization requirements
-
-**Business Logic:**
-- Core methods and roles
-- Validation rules
-- External service integrations
-
-**Data Flow:**
-- Related tables/models
-- Relationships (1:N, N:M)
-- Key query patterns
-
-#### 5. Output Analysis Results
-
-```markdown
-## 📊 [feature-name] Analysis Results
-
-### Overview
-- **Feature description**: [one-line summary]
-- **Implementation status**: [Complete/In progress/Not implemented]
-- **Related files**: N files
-
-### Structure
-
-#### API Endpoints
-| Method | Path | Description | Auth |
-|--------|------|-------------|------|
-| POST | /api/v1/auth/login | Login | - |
-
-#### Core Services
-- `auth_service.py`: Authentication logic
-  - `login()`: Login processing
-  - `verify_token()`: Token verification
-
-#### Data Models
-- `User`: User table
-  - Key fields: id, email, password_hash
-  - Relationships: Session (1:N)
-
-### Flow Diagram
-[Text-based flow description]
-
-### Reference File List
-- src/api/auth/router.py:L10-50
-- src/services/auth_service.py:L1-100
-```
-
-#### 6. Check Development Rules
-
-Load related rules from `.vibe/rules/`:
-- `core/quick-start.md` - 5 core principles
-- `standards/complexity-metrics.md` - Complexity standards
-- `quality/checklist.md` - Quality checklist
-
-Output any rule violations found.
-
-#### 7. Complete
-
-After analysis:
-1. Output analysis summary
-2. Ask "What would you like me to help with?"
-3. Use collected context for subsequent development/modification requests
-
----
-
-## Mode 2: Project Quality Analysis (no option or --code/--deps/--arch)
-
-### Analysis Scope
-
-- **Default** (`/vibe.analyze`): Full analysis (code + dependencies + architecture)
-- **--code**: Code quality analysis only
-- **--deps**: Dependency analysis only
-- **--arch**: Architecture analysis only
-
-### MCP Tool Usage
-
-Based on `@su-record/hi-ai`:
-
-#### Code Quality Analysis (--code)
-- `analyze_complexity`: Complexity analysis
-- `validate_code_quality`: Code quality validation
-- `check_coupling_cohesion`: Coupling/cohesion check
-
-#### Dependency Analysis (--deps)
-- Read `package.json` / `pyproject.toml` / `pubspec.yaml`
-- Analyze version conflicts, security vulnerabilities, packages needing updates
-
-#### Architecture Analysis (--arch)
-- `find_symbol`: Find core modules
-- `find_references`: Identify module dependencies
-- Detect circular dependencies, layer violations
-
-### Analysis Report
-
-`.vibe/reports/analysis-{date}.md`:
-
-```markdown
-# Project Analysis Report
-
-## Overview
-- Analysis date: 2025-01-06 12:00
-- Analysis scope: Full
-
-## Code Quality (85/100)
-- Average complexity: 8.2 (good)
-- High complexity files: 3
-
-## Dependencies (92/100)
-- Total packages: 42
-- Updates needed: 3
-
-## Architecture (78/100)
-- Circular dependencies: 2 found
-- Layer violations: 1
-
-## Improvement Suggestions
-1. Refactor service.py
-2. Apply lodash security patch
-```
-
----
-
-## Example
-
-### Feature Analysis
-```
-User: /vibe.analyze "login"
-
-Claude: Analyzing login related code...
-
-[Exploring code with Glob, Grep, Read tools]
-
-📊 Login Analysis Results
-
-### Overview
-- Feature description: JWT-based user authentication
-- Implementation status: Complete
-- Related files: 8
-
-### API Endpoints
-| POST | /api/v1/auth/login | Login | - |
-| POST | /api/v1/auth/refresh | Token refresh | Required |
-
-[Analysis continues...]
-
-What would you like me to help with?
-- Refactoring
-- Add new feature
-- Bug fix
-```
-
-### Quality Analysis
-```
-User: /vibe.analyze --code
-
-Claude: Starting code quality analysis...
-
-📊 Code Quality Score: 85/100 (B+)
-
-**Key findings:**
-- High complexity: src/service.py (CC: 15)
-
-**Improvement suggestions:**
-1. Split src/service.py into 3 modules
-```
-
----
-
-ARGUMENTS: $ARGUMENTS

package/.claude/commands/vibe.compound.md

@@ -1,261 +0,0 @@
----
-description: Auto-document solutions for knowledge compounding
-argument-hint: "solution description (optional)"
----
-
-# /vibe.compound
-
-**Knowledge Compounding** - Auto-document solved problems to boost future productivity
-
-> "Each solution documented makes future problems easier to solve."
-
-## Usage
-
-```
-/vibe.compound                           # Auto-detect recent solutions
-/vibe.compound "Redis cache invalidation" # Document specific solution
-```
-
-## Auto-Triggers
-
-Automatically suggested when these patterns detected:
-- "it's fixed", "fixed", "solved", "resolved"
-- After PR merge
-- After `/vibe.verify` passes
-
-## Process
-
-### Phase 1: Solution Extraction
-
-Parallel agents analyze the solution:
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│  🔍 PARALLEL SOLUTION ANALYSIS                                   │
-├─────────────────────────────────────────────────────────────────┤
-│                                                                 │
-│  Task 1: problem-analyzer                                       │
-│  ├── Identify original problem                                  │
-│  ├── Symptoms and error messages                                │
-│  └── Impact scope                                               │
-│                                                                 │
-│  Task 2: solution-extractor                                     │
-│  ├── Applied fixes                                              │
-│  ├── Key code changes                                           │
-│  └── Configuration changes                                      │
-│                                                                 │
-│  Task 3: root-cause-analyzer                                    │
-│  ├── Root cause identification                                  │
-│  ├── Why it happened                                            │
-│  └── Prevention methods                                         │
-│                                                                 │
-│  Task 4: pattern-recognizer                                     │
-│  ├── Similar problem patterns                                   │
-│  ├── Related tech stack                                         │
-│  └── Search keywords                                            │
-│                                                                 │
-│  Task 5: category-classifier                                    │
-│  ├── Category classification                                    │
-│  ├── Tag generation                                             │
-│  └── Related doc links                                          │
-│                                                                 │
-│  Task 6: code-snippet-extractor                                 │
-│  ├── Before/After code                                          │
-│  ├── Key change highlights                                      │
-│  └── Copy-paste snippets                                        │
-│                                                                 │
-│  Task 7: prevention-advisor                                     │
-│  ├── Prevention checklist                                       │
-│  ├── Suggested linter rules                                     │
-│  └── Test case suggestions                                      │
-│                                                                 │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-### Phase 2: Category Classification
-
-```
-.vibe/solutions/
-├── security/           # Security related
-│   ├── sql-injection-prevention.md
-│   └── xss-sanitization.md
-├── performance/        # Performance optimization
-│   ├── n1-query-fix.md
-│   └── redis-cache-invalidation.md
-├── database/           # Database related
-│   ├── migration-rollback.md
-│   └── deadlock-resolution.md
-├── integration/        # External integrations
-│   ├── stripe-webhook-retry.md
-│   └── aws-s3-timeout.md
-├── frontend/           # Frontend issues
-│   ├── react-hydration-mismatch.md
-│   └── infinite-scroll-memory.md
-├── testing/            # Testing related
-│   ├── flaky-test-fix.md
-│   └── mock-timezone.md
-└── deployment/         # Deployment issues
-    ├── docker-layer-cache.md
-    └── k8s-rolling-update.md
-```
-
-### Phase 3: Document Generation
-
-```markdown
-# [Solution] Redis Cache Invalidation
-
-## TL;DR
-Added version suffix to Redis cache key to fix invalidation issue
-
-## Problem
-### Symptoms
-- User profile shows stale data after update
-- Refresh doesn't fix the issue
-
-### Error/Logs
-```
-Cache hit: user:123 (stale data)
-```
-
-### Impact Scope
-- User profile page
-- API: GET /api/users/:id
-
-## Root Cause
-Cache key only used user_id, not invalidated on update
-
-```python
-# Before
-cache_key = f"user:{user_id}"  # No version
-```
-
-## Solution
-### Key Change
-Add updated_at timestamp to cache key
-
-```python
-# After
-cache_key = f"user:{user_id}:v{updated_at.timestamp()}"
-```
-
-### Changed Files
-- src/services/cache.py:42
-- src/api/users.py:78
-
-## Prevention
-- [ ] Always include version/timestamp in cache keys
-- [ ] Add cache invalidation tests
-- [ ] Linter rule: cache_key pattern check
-
-## Related
-- Similar issue: #234 (Session cache)
-- Docs: docs/caching-strategy.md
-- Tags: #redis #cache #invalidation
-
-## Metadata
-- Resolved: 2026-01-11
-- Time spent: 2 hours
-- Difficulty: Medium
-- Reusability: High
-```
-
-### Phase 4: Index Update
-
-Auto-update `.vibe/solutions/index.md`:
-
-```markdown
-# Solution Index
-
-## Recently Added
-| Date | Category | Title | Tags |
-|------|----------|-------|------|
-| 2026-01-11 | performance | Redis cache invalidation | #redis #cache |
-| 2026-01-10 | security | SQL Injection prevention | #sql #security |
-
-## By Category
-- **Security** (5 solutions)
-- **Performance** (8 solutions)
-- **Database** (4 solutions)
-...
-
-## Search Keywords
-- redis → performance/redis-cache-invalidation.md
-- n+1 → performance/n1-query-fix.md
-- sql injection → security/sql-injection-prevention.md
-```
-
-## Auto-Suggestion
-
-When similar problem detected:
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│  💡 Similar Solution Found!                                      │
-├─────────────────────────────────────────────────────────────────┤
-│                                                                 │
-│  You're working on: "Cache not updating"                        │
-│                                                                 │
-│  Related solution (85% match):                                  │
-│  📄 .vibe/solutions/performance/redis-cache-invalidation.md     │
-│                                                                 │
-│  Key insight: Add version suffix to cache key                   │
-│                                                                 │
-│  Apply this solution? [Y/n]                                     │
-│                                                                 │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-## Output
-
-```
-┌─────────────────────────────────────────────────────────────────┐
-│  📚 SOLUTION DOCUMENTED                                          │
-├─────────────────────────────────────────────────────────────────┤
-│                                                                 │
-│  ✅ Created: .vibe/solutions/performance/redis-cache-invalid... │
-│                                                                 │
-│  📊 Knowledge Base Stats:                                        │
-│  ├── Total Solutions: 42                                        │
-│  ├── This Month: 8                                              │
-│  └── Most Used Category: performance                            │
-│                                                                 │
-│  🔗 Similar solutions linked: 2                                  │
-│  🏷️ Tags: #redis #cache #invalidation #performance              │
-│                                                                 │
-│  💡 Prevention rules added to .vibe/rules/                       │
-│                                                                 │
-│  "This solution will help future you (or teammates) save hours" │
-│                                                                 │
-└─────────────────────────────────────────────────────────────────┘
-```
-
-## Integration with Memory
-
-Auto-invoke `vibe_save_memory`:
-
-```json
-{
-  "type": "solution",
-  "category": "performance",
-  "title": "Redis cache invalidation",
-  "keywords": ["redis", "cache", "invalidation"],
-  "file": ".vibe/solutions/performance/redis-cache-invalidation.md"
-}
-```
-
-## Workflow Integration
-
-```
-/vibe.spec → /vibe.run → /vibe.verify → /vibe.compound
-                                              │
-                                              ▼
-                                    .vibe/solutions/
-                                              │
-                                              ▼
-                                    Future problem?
-                                    Auto-suggest!
-```
-
----
-
-ARGUMENTS: $ARGUMENTS

package/.claude/commands/vibe.continue.md

@@ -1,88 +0,0 @@
----
-description: Restore previous session context
-argument-hint: [projectPath]
----
-
-# /vibe.continue
-
-Restore previous session context and continue development.
-
-## Usage
-
-```
-/vibe.continue                    # Restore context for current directory
-/vibe.continue "/path/to/project" # Restore context for specific project
-```
-
-## What It Does
-
-1. **Load Project Memories** - Retrieves saved project decisions, patterns, architecture notes
-2. **Restore Context** - Loads previous session's work state (tasks, blockers, next steps)
-3. **Load Coding Guides** - Applies project-specific coding standards
-
-## Process
-
-```
-/vibe.continue
-      |
-      v
-+---------------------------+
-| vibe_start_session  |
-| projectPath: $(pwd)       |
-+---------------------------+
-      |
-      v
-+---------------------------+
-| Load:                     |
-| - Project memories        |
-| - Previous context        |
-| - Coding guides           |
-+---------------------------+
-      |
-      v
-Ready to continue!
-```
-
-## Example
-
-```
-User: /vibe.continue
-
-Claude:
-Session started.
-
-Recent Project Info:
-  - project-stack: Next.js 14, TypeScript, Tailwind...
-  - auth-decision: Using JWT with refresh tokens...
-  - current-feature: Working on login page...
-
-Previous Context:
-  - HIGH priority from 2024-01-15 14:32
-    Task: Implement password validation
-    Blockers: Need to decide on complexity rules
-
-Active Coding Guides:
-  - TypeScript Standards (core): Strict mode, no any...
-
-Ready to continue development! What would you like to work on?
-```
-
-## When to Use
-
-- Starting a new Claude Code session
-- After `/new` command
-- Resuming work after a break
-- Switching between projects
-
-## Related Commands
-
-- `/vibe.run` - Execute implementation
-- `/vibe.spec` - Create SPEC document
-
----
-
-**Action**: Call `vibe_start_session` with projectPath
-
-```
-vibe_start_session(projectPath: "$ARGUMENTS" || process.cwd())
-```