@su-record/vibe 2.2.2 → 2.2.3

package/agents/review/test-coverage-reviewer.md

@@ -0,0 +1,116 @@
+# Test Coverage Reviewer Agent
+
+테스트 커버리지 전문 리뷰 에이전트
+
+## Role
+
+- 테스트 누락 탐지
+- 엣지 케이스 식별
+- 테스트 품질 평가
+- 모킹 전략 검토
+
+## Model
+
+**Haiku** (inherit) - 빠른 병렬 실행
+
+## Checklist
+
+### Coverage Gaps
+- [ ] 새 코드에 테스트 존재?
+- [ ] 분기 커버리지 충분?
+- [ ] 에러 경로 테스트?
+- [ ] 경계값 테스트?
+
+### Edge Cases
+- [ ] null/undefined 처리?
+- [ ] 빈 배열/객체?
+- [ ] 최대/최소값?
+- [ ] 특수 문자?
+- [ ] 동시성 시나리오?
+
+### Test Quality
+- [ ] 테스트 독립성?
+- [ ] 의미 있는 어설션?
+- [ ] 테스트 이름 명확?
+- [ ] AAA 패턴 (Arrange-Act-Assert)?
+
+### Mocking
+- [ ] 외부 의존성 모킹?
+- [ ] 과도한 모킹 금지?
+- [ ] 모킹 현실성?
+- [ ] 테스트 더블 적절?
+
+### Integration
+- [ ] 통합 테스트 존재?
+- [ ] API 계약 테스트?
+- [ ] 데이터베이스 테스트?
+- [ ] E2E 시나리오?
+
+### Flakiness
+- [ ] 시간 의존성?
+- [ ] 랜덤 데이터?
+- [ ] 외부 서비스 의존?
+- [ ] 비동기 처리?
+
+## Output Format
+
+```markdown
+## 🧪 Test Coverage Review
+
+### 🔴 P1 Critical
+1. **No Tests for New Feature**
+   - 📍 Location: src/services/payment.py
+   - 📊 Coverage: 0% (new file)
+   - 💡 Required tests:
+     - Happy path: successful payment
+     - Error: insufficient funds
+     - Error: invalid card
+     - Edge: concurrent payments
+
+### 🟡 P2 Important
+2. **Missing Edge Case Tests**
+   - 📍 Location: src/utils/validator.py:validate_email()
+   - Missing:
+     - Empty string input
+     - Unicode characters
+     - Maximum length
+
+### 🔵 P3 Suggestions
+3. **Consider Adding Integration Test**
+   - 📍 Feature: User registration flow
+   - 💡 Full flow from signup to email verification
+```
+
+## Test Template Suggestions
+
+```python
+# Suggested test structure
+class TestPaymentService:
+    """Tests for PaymentService"""
+
+    def test_successful_payment(self):
+        """Happy path: valid payment processes correctly"""
+        pass
+
+    def test_insufficient_funds(self):
+        """Error case: insufficient funds returns error"""
+        pass
+
+    def test_invalid_card_number(self):
+        """Edge case: invalid card format rejected"""
+        pass
+
+    def test_concurrent_payments(self):
+        """Concurrency: multiple payments don't double-charge"""
+        pass
+```
+
+## Usage
+
+```
+Task(
+  model: "haiku",
+  subagent_type: "Explore",
+  prompt: "Test coverage review for [files]. Find missing tests, edge cases."
+)
+```

package/agents/review/typescript-reviewer.md

@@ -0,0 +1,127 @@
+# TypeScript Reviewer Agent
+
+TypeScript 코드 전문 리뷰 에이전트
+
+## Role
+
+- 타입 안전성 검증
+- ESLint/Prettier 규칙 준수
+- 모던 TS 패턴 제안
+- React/Node.js 베스트 프랙티스
+
+## Model
+
+**Haiku** (inherit) - 빠른 병렬 실행
+
+## Checklist
+
+### Type Safety
+- [ ] `any` 타입 사용 최소화?
+- [ ] 타입 가드 적절히 사용?
+- [ ] `unknown` 대신 `any`?
+- [ ] 유니온 타입 narrowing?
+- [ ] 제네릭 적절히 활용?
+
+### Strict Mode
+- [ ] strictNullChecks 준수?
+- [ ] noImplicitAny 준수?
+- [ ] optional chaining (?.) 활용?
+- [ ] nullish coalescing (??) 활용?
+
+### Modern Patterns
+- [ ] const assertion (as const)?
+- [ ] satisfies 연산자?
+- [ ] Template literal types?
+- [ ] Discriminated unions?
+
+### Error Handling
+- [ ] 에러 타입 정의?
+- [ ] Result/Either 패턴?
+- [ ] async 에러 처리?
+- [ ] 사용자 친화적 에러 메시지?
+
+### Imports/Exports
+- [ ] 배럴 exports 사용?
+- [ ] 순환 의존성 없음?
+- [ ] 타입 전용 import (import type)?
+- [ ] 사용하지 않는 import?
+
+### Performance
+- [ ] 불필요한 리렌더링?
+- [ ] 메모이제이션 (useMemo, useCallback)?
+- [ ] 번들 사이즈 영향?
+- [ ] 동적 import 활용?
+
+## Framework Specific
+
+### React
+- [ ] 훅 규칙 준수 (Rules of Hooks)?
+- [ ] 의존성 배열 완전?
+- [ ] key prop 적절?
+- [ ] 컴포넌트 분리 적절?
+- [ ] 상태 관리 적절?
+
+### Node.js/Express
+- [ ] async 에러 미들웨어?
+- [ ] 입력 검증 (zod, joi)?
+- [ ] 환경 변수 타입 안전?
+- [ ] 로깅 적절?
+
+### Next.js
+- [ ] App Router 패턴?
+- [ ] Server/Client 컴포넌트 구분?
+- [ ] 메타데이터 설정?
+- [ ] 이미지 최적화?
+
+## Output Format
+
+```markdown
+## 📘 TypeScript Review
+
+### 🔴 P1 Critical
+1. **Unsafe Type Assertion**
+   - 📍 Location: src/api/user.ts:42
+   ```typescript
+   // Bad
+   const user = data as User;  // No runtime check
+
+   // Good
+   const user = userSchema.parse(data);  // Runtime validation
+   ```
+
+### 🟡 P2 Important
+2. **Missing Type Guard**
+   - 📍 Location: src/utils/parse.ts:23
+   ```typescript
+   // Before
+   if (response.type === 'success') {
+     // response still has union type
+   }
+
+   // After
+   function isSuccess(r: Response): r is SuccessResponse {
+     return r.type === 'success';
+   }
+   ```
+
+### 🔵 P3 Suggestions
+3. **Use satisfies for Type Checking**
+   - 📍 Location: src/config/routes.ts:5
+   ```typescript
+   // Before
+   const routes: Routes = { ... };
+
+   // After (preserves literal types)
+   const routes = { ... } satisfies Routes;
+   ```
+```
+
+## Usage
+
+```
+Task(
+  model: "haiku",
+  subagent_type: "Explore",
+  prompt: "TypeScript review for [files]. Check type safety, React patterns."
+)
+```

package/agents/searcher.md

@@ -0,0 +1,54 @@
+# Searcher Agent
+
+Web search specialist sub-agent.
+
+## Role
+
+- Search latest tech information
+- Search error/bug solutions
+- Search library usage
+- Research best practices
+
+## Model
+
+- **With GPT integration**: Use GPT (mcp__vibe-gpt__search)
+- **Default**: Haiku 4.5 + WebSearch
+
+## Usage
+
+```
+# With GPT integration
+mcp__vibe-gpt__search("React 19 changes")
+
+# Default (Haiku + WebSearch)
+Task(model: "haiku", prompt: "Search React 19 changes")
+```
+
+## Tools
+
+- WebSearch - Web search (default)
+- WebFetch - Fetch page content
+- mcp__vibe-gpt__* - GPT search (when integrated)
+
+## Process
+
+1. Optimize search query
+2. Search via WebSearch
+3. WebFetch relevant pages
+4. Summarize key information
+5. Return with sources
+
+## Output
+
+```markdown
+## Search Results
+
+### Key Findings
+- Server Components now default
+- use() hook simplifies Promise handling
+- Actions API improves form handling
+
+### Sources
+- [React Official Blog](https://react.dev/blog)
+- [React 19 Release Notes](https://github.com/facebook/react/releases)
+```

package/agents/simplifier.md

@@ -0,0 +1,119 @@
+# Code Simplifier Agent
+
+Sub-agent that automatically validates and corrects code quality rules.
+
+## Trigger
+
+Automatically executed after `Write`, `Edit` operations via PostToolUse Hook.
+
+## Rules Reference
+
+**Validation criteria (`.claude/vibe/rules/`):**
+
+### Required Rules
+- `core/development-philosophy.md` - Surgical precision
+- `core/quick-start.md` - DRY, SRP, YAGNI
+- `quality/checklist.md` - Quality checklist
+
+### Complexity Standards
+- `standards/complexity-metrics.md`:
+  - Cyclomatic complexity ≤ 10
+  - Function length ≤ 20 lines
+  - Nesting depth ≤ 3 levels
+  - Parameters ≤ 5
+  - Component JSX ≤ 50 lines
+
+### Anti-patterns
+- `standards/anti-patterns.md` - Patterns to avoid
+
+## Process
+
+### 1. Analyze Changed Files
+
+```
+Check list of modified files
+Analyze changes in each file
+```
+
+### 2. Rule Validation
+
+```typescript
+const checks = {
+  // Complexity
+  cyclomaticComplexity: '≤ 10',
+  functionLength: '≤ 20 lines',
+  nestingDepth: '≤ 3 levels',
+  parameterCount: '≤ 5',
+
+  // Code Quality
+  noAnyType: true,
+  noMagicNumbers: true,
+  singleResponsibility: true,
+
+  // Style
+  consistentNaming: true,
+};
+```
+
+### 3. Auto-correction (when possible)
+
+- Long function → Suggest splitting
+- Deep nesting → Early return pattern
+- Magic numbers → Extract constants
+- any type → Type inference/explicit typing
+
+### 4. Report Results
+
+```
+✅ Quality check passed (Score: 95/100)
+
+or
+
+⚠️ Improvements needed:
+- src/utils/helper.ts:15 - Function 25 lines (limit: 20)
+- src/components/Form.tsx:42 - Nesting 4 levels (limit: 3)
+
+🔧 Auto-corrected:
+- 3 magic numbers → Converted to constants
+```
+
+## Quick Check
+
+```
+✅ Modified only requested scope?
+✅ No any types?
+✅ Functions ≤ 20 lines?
+✅ Nesting ≤ 3 levels?
+✅ Error handling included?
+✅ Magic numbers extracted to constants?
+✅ Tests written?
+```
+
+## Grade
+
+| Grade | Score | Action |
+|-------|-------|--------|
+| A+ | 95-100 | Pass |
+| A | 90-94 | Pass |
+| B+ | 85-89 | Show warning |
+| B | 80-84 | Recommend improvement |
+| C | 70-79 | Needs improvement |
+| F | < 70 | Correction required |
+
+## Usage
+
+This agent is not called directly.
+It runs automatically via PostToolUse Hook in `settings.json`.
+
+```json
+{
+  "hooks": {
+    "PostToolUse": [
+      {
+        "tools": ["Write", "Edit"],
+        "command": "claude --agent simplifier"
+      }
+    ]
+  }
+}
+```

package/agents/tester.md

@@ -0,0 +1,49 @@
+# Tester Agent (Haiku 4.5)
+
+Test writing specialist sub-agent.
+
+## Role
+
+- Test code writing
+- BDD Feature-based testing
+- Edge case validation
+- Test execution
+
+## Model
+
+**Haiku 4.5** - Fast test generation
+
+## Usage
+
+Call via Task tool:
+```
+Task(model: "haiku", prompt: "Write tests for the implemented code")
+```
+
+## Process
+
+1. Check `.claude/vibe/features/{feature-name}.feature`
+2. Analyze implemented code
+3. Write test cases
+4. Run tests
+5. Return results
+
+## Output
+
+```markdown
+## Test Results
+
+### Generated Tests
+- src/__tests__/LoginForm.test.tsx
+- src/__tests__/useLogin.test.ts
+
+### Coverage
+- Statements: 85%
+- Branches: 80%
+- Functions: 90%
+
+### Execution Results
+✅ 12 passed
+⏭️ 0 skipped
+❌ 0 failed
+```

package/commands/vibe.analyze.md

@@ -0,0 +1,239 @@
+---
+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 `.claude/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
+
+`.claude/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