@su-record/vibe 2.2.4 → 2.3.0

package/commands/vibe.analyze.md

@@ -1,6 +1,6 @@
 ---
 description: Analyze project or specific feature/module
-argument-hint: "feature-name" or --code or --deps or --arch (optional)
+argument-hint: "feature-name" or --code or --deps or --arch
 ---
 
 # /vibe.analyze
@@ -17,7 +17,7 @@ Analyze project or specific feature/module.
 /vibe.analyze --arch           # Architecture analysis only
 ```
 
-## ⚠️ Context Reset
+## Context Reset
 
 **When this command runs, previous conversation is ignored.**
 - Explore and analyze code from scratch like new session
@@ -83,7 +83,7 @@ Read `CLAUDE.md`, `package.json`, `pyproject.toml`, etc. to identify tech stack:
 #### 5. Output Analysis Results
 
 ```markdown
-## 📊 [feature-name] Analysis Results
+## [feature-name] Analysis Results
 
 ### Overview
 - **Feature description**: [one-line summary]
@@ -107,24 +107,12 @@ Read `CLAUDE.md`, `package.json`, `pyproject.toml`, etc. to identify tech stack:
   - 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
+#### 6. Complete
 
 After analysis:
 1. Output analysis summary
@@ -133,7 +121,7 @@ After analysis:
 
 ---
 
-## Mode 2: Project Quality Analysis (no option or --code/--deps/--arch)
+## Mode 2: Project Quality Analysis (--code/--deps/--arch)
 
 ### Analysis Scope
 
@@ -142,22 +130,21 @@ After analysis:
 - **--deps**: Dependency analysis only
 - **--arch**: Architecture analysis only
 
-### MCP Tool Usage
+### Code Quality Analysis (--code)
 
-Based on `@su-record/hi-ai`:
+- Complexity analysis (Cyclomatic Complexity)
+- Code quality validation
+- Coupling/cohesion check
 
-#### Code Quality Analysis (--code)
-- `analyze_complexity`: Complexity analysis
-- `validate_code_quality`: Code quality validation
-- `check_coupling_cohesion`: Coupling/cohesion check
+### Dependency Analysis (--deps)
 
-#### 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
+### Architecture Analysis (--arch)
+
+- Find core modules
+- Identify module dependencies
 - Detect circular dependencies, layer violations
 
 ### Analysis Report
@@ -190,50 +177,4 @@ Based on `@su-record/hi-ai`:
 
 ---
 
-## 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/commands/vibe.reason.md

@@ -5,7 +5,7 @@ argument-hint: "problem description"
 
 # /vibe.reason
 
-Apply 9-step reasoning framework to complex problems (Reasoning Agent).
+Apply 9-step reasoning framework to complex problems.
 
 ## Usage
 
@@ -13,35 +13,15 @@ Apply 9-step reasoning framework to complex problems (Reasoning Agent).
 /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
+1. **Complex bug debugging** - Root cause unclear, need systematic hypothesis verification
+2. **Architecture design decisions** - Choose optimal option among several
+3. **Performance optimization** - Bottleneck may be in multiple places
+4. **Refactoring planning** - Systematically analyze legacy code complexity
+5. **Requirements analysis** - Reconcile conflicting requirements
 
-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
+## 9-Step Reasoning Framework
 
 ### 1. Logical Dependencies and Constraints
 - Check policies, rules, prerequisites
@@ -89,17 +69,6 @@ Use in situations like:
 - 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
@@ -113,12 +82,6 @@ This command automatically uses these MCP tools:
 
 ## 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]
 
@@ -126,180 +89,94 @@ This command automatically uses these MCP tools:
 
 ## 2. Risk Assessment
 
-...
+**Risk Assessment**:
+- Task type: [risk level]
+- Rollback possibility: [assessment]
+- Compatibility/Security/Performance risks
+
+---
+
+## 3. Inductive Reasoning and Hypothesis Exploration
+
+**Hypothesis Generation**:
+1. **Hypothesis 1**: [description] (Likelihood: High/Medium/Low)
+   - Evidence: [supporting evidence]
+   - Verification: [how to verify]
+
+2. **Hypothesis 2**: ...
+
+---
+
+[Steps 4-9...]
 
 ---
 
 ## Summary
 
 [Overall reasoning results summary and recommendations]
-```
 
-## Examples
+**Recommended Actions**:
+1. Immediate: [low risk action]
+2. Short-term: [medium priority]
+3. Medium-term: [long-term fix]
+```
 
-### Example 1: Complex Bug Debugging
+## Example
 
 ```
-User: /vibe.reason "After user login, profile page intermittently returns 500 error. Log shows 'TypeError: Cannot read property id of undefined'"
+User: /vibe.reason "After user login, profile page intermittently returns 500 error"
 
-AI: Analyzing this problem with 9-step reasoning framework.
+AI: Analyzing with 9-step reasoning framework...
 
 # Reasoning Framework Analysis
 
-**Problem**: Intermittent 500 error on profile page after login (TypeError: Cannot read property 'id' of undefined)
+**Problem**: Intermittent 500 error on profile page after login
 **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
+- 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
+   - Verification: Add logging to session save logic
 
 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...]
-
----
+   - Verification: Check Promise chain, missing await
 
 ## 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
+- Most likely cause: Incomplete session data
+- Verification priority: 1) Session logging -> 2) Async review -> 3) DB check
 
 **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. Immediate: Add detailed logging to session save/fetch
+2. Short-term: Code review async processing
+3. Medium-term: Strengthen session store monitoring
 ```
-# 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"
+   - Bad: "There's a bug"
+   - Good: "After login, profile page intermittently returns 500 error"
 
 2. **Include context**
-   - Occurrence conditions (always? intermittent? specific conditions only?)
+   - Occurrence conditions (always? intermittent?)
    - 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)
+3. **Verify step by step**
+   - Verify hypotheses in order of likelihood
+   - Feedback each verification result
 
 ---