@su-record/vibe 2.8.48 → 2.8.50

package/dist/infra/lib/SkillFrontmatter.js

@@ -198,33 +198,33 @@ export function substituteTemplateVars(template, vars) {
 /**
  * Example skill template
  */
-export const SKILL_TEMPLATE_EXAMPLE = `---
-name: example-skill
-description: "An example skill demonstrating the frontmatter system"
-model: sonnet
-agent: implementer
-argument-hint: "task description"
-user-invocable: true
-triggers: [example, demo, test]
-priority: 50
----
-
-# Example Skill
-
-This skill demonstrates the frontmatter metadata system.
-
-## Arguments
-
-$ARGUMENTS
-
-## Process
-
-1. Parse the arguments
-2. Execute the task
-3. Return the result
-
-## Output
-
-Provide a clear summary of what was done.
+export const SKILL_TEMPLATE_EXAMPLE = `---
+name: example-skill
+description: "An example skill demonstrating the frontmatter system"
+model: sonnet
+agent: implementer
+argument-hint: "task description"
+user-invocable: true
+triggers: [example, demo, test]
+priority: 50
+---
+
+# Example Skill
+
+This skill demonstrates the frontmatter metadata system.
+
+## Arguments
+
+$ARGUMENTS
+
+## Process
+
+1. Parse the arguments
+2. Execute the task
+3. Return the result
+
+## Output
+
+Provide a clear summary of what was done.
 `;
 //# sourceMappingURL=SkillFrontmatter.js.map

package/dist/infra/lib/SkillQualityGate.js

@@ -137,15 +137,15 @@ export function suggestPrincipleFormat(value) {
         return value;
     }
     // 변환 템플릿 제안
-    return `Consider reformulating as:
-
-"When [describe the situation/trigger],
-[describe the action to take]
-because [explain the reasoning/tradeoff]"
-
-Example:
-"When the auth token expires during a request,
-retry the request after refreshing the token (not before)
+    return `Consider reformulating as:
+
+"When [describe the situation/trigger],
+[describe the action to take]
+because [explain the reasoning/tradeoff]"
+
+Example:
+"When the auth token expires during a request,
+retry the request after refreshing the token (not before)
 because refreshing preemptively causes race conditions with concurrent requests"`;
 }
 /**

package/dist/infra/lib/SkillRepository.js

@@ -285,177 +285,177 @@ export function getDefaultSkills(corePathUrl) {
     return [
         {
             id: 'multi-llm-orchestration',
-            content: `---
-name: multi-llm-orchestration
-description: "Multi-LLM research using GPT and Gemini for comprehensive analysis"
-triggers: [gpt, gemini, multi-llm, research, parallel research]
-priority: 80
----
-# Multi-LLM Orchestration
-
-Use multiple LLMs for comprehensive research and validation.
-
-## Usage
-
-\`\`\`bash
-# Via Bash hook (automatic in /vibe.spec)
-node hooks/scripts/llm-orchestrate.js gpt "your prompt"
-node hooks/scripts/llm-orchestrate.js gemini "your prompt"
-\`\`\`
-
-## Setup
-
-\`\`\`bash
-vibe gpt auth     # Configure GPT API key
-vibe gemini auth  # Configure Gemini API key
-vibe status       # Check current configuration
-\`\`\`
-
-## Best Practices
-
-1. Use GPT for best practices and code review
-2. Use Gemini for documentation and security analysis
-3. Combine results for comprehensive coverage
+            content: `---
+name: multi-llm-orchestration
+description: "Multi-LLM research using GPT and Gemini for comprehensive analysis"
+triggers: [gpt, gemini, multi-llm, research, parallel research]
+priority: 80
+---
+# Multi-LLM Orchestration
+
+Use multiple LLMs for comprehensive research and validation.
+
+## Usage
+
+\`\`\`bash
+# Via Bash hook (automatic in /vibe.spec)
+node hooks/scripts/llm-orchestrate.js gpt "your prompt"
+node hooks/scripts/llm-orchestrate.js gemini "your prompt"
+\`\`\`
+
+## Setup
+
+\`\`\`bash
+vibe gpt auth     # Configure GPT API key
+vibe gemini auth  # Configure Gemini API key
+vibe status       # Check current configuration
+\`\`\`
+
+## Best Practices
+
+1. Use GPT for best practices and code review
+2. Use Gemini for documentation and security analysis
+3. Combine results for comprehensive coverage
 `,
         },
         {
             id: 'error-recovery',
-            content: `---
-name: error-recovery
-description: "Error recovery patterns and retry strategies"
-triggers: [error, fail, retry, recover, fix]
-priority: 70
----
-# Error Recovery Patterns
-
-## Common Error Types
-
-### Build Errors
-- Check TypeScript compilation errors
-- Verify dependency versions
-- Run \`npm ci\` to clean install
-
-### Test Failures
-- Run failed tests in isolation
-- Check test fixtures/mocks
-- Verify async timing issues
-
-### Runtime Errors
-- Check stack trace carefully
-- Verify environment variables
-- Check external service connectivity
-
-## Retry Strategy
-
-1. First retry: Same action
-2. Second retry: Clean state (cache clear)
-3. Third retry: Alternative approach
-4. Max retries exceeded: Escalate to user
-
-## Auto-Recovery Commands
-
-\`\`\`bash
-# Clean build
-rm -rf node_modules dist && npm ci && npm run build
-
-# Reset git state (careful!)
-git stash && git checkout .
-
-# Clear caches
-npm cache clean --force
-\`\`\`
+            content: `---
+name: error-recovery
+description: "Error recovery patterns and retry strategies"
+triggers: [error, fail, retry, recover, fix]
+priority: 70
+---
+# Error Recovery Patterns
+
+## Common Error Types
+
+### Build Errors
+- Check TypeScript compilation errors
+- Verify dependency versions
+- Run \`npm ci\` to clean install
+
+### Test Failures
+- Run failed tests in isolation
+- Check test fixtures/mocks
+- Verify async timing issues
+
+### Runtime Errors
+- Check stack trace carefully
+- Verify environment variables
+- Check external service connectivity
+
+## Retry Strategy
+
+1. First retry: Same action
+2. Second retry: Clean state (cache clear)
+3. Third retry: Alternative approach
+4. Max retries exceeded: Escalate to user
+
+## Auto-Recovery Commands
+
+\`\`\`bash
+# Clean build
+rm -rf node_modules dist && npm ci && npm run build
+
+# Reset git state (careful!)
+git stash && git checkout .
+
+# Clear caches
+npm cache clean --force
+\`\`\`
 `,
         },
         {
             id: 'code-quality-check',
-            content: `---
-name: code-quality-check
-description: "Code quality validation using core tools"
-triggers: [quality, lint, complexity, review]
-priority: 60
----
-# Code Quality Check
-
-## Using Core Tools
-
-\`\`\`bash
-# Analyze complexity
-node -e "import('${corePathUrl}/node_modules/@su-record/vibe/dist/tools/index.js').then(t =>
-  t.analyzeComplexity({targetPath: 'src/', projectPath: process.cwd()})
-  .then(r => console.log(r.content[0].text))
-)"
-
-# Validate quality
-node -e "import('${corePathUrl}/node_modules/@su-record/vibe/dist/tools/index.js').then(t =>
-  t.validateCodeQuality({targetPath: 'src/', projectPath: process.cwd()})
-  .then(r => console.log(r.content[0].text))
-)"
-\`\`\`
-
-## Quality Metrics
-
-| Metric | Good | Warning | Critical |
-|--------|------|---------|----------|
-| Cyclomatic Complexity | ≤10 | 11-15 | >15 |
-| Function Length | ≤30 | 31-50 | >50 |
-| Nesting Depth | ≤3 | 4 | >4 |
-
-## Common Issues
-
-1. **High Complexity**: Extract helper functions
-2. **Long Functions**: Split by responsibility
-3. **Deep Nesting**: Use early returns
-4. **Tight Coupling**: Apply dependency injection
+            content: `---
+name: code-quality-check
+description: "Code quality validation using core tools"
+triggers: [quality, lint, complexity, review]
+priority: 60
+---
+# Code Quality Check
+
+## Using Core Tools
+
+\`\`\`bash
+# Analyze complexity
+node -e "import('${corePathUrl}/node_modules/@su-record/vibe/dist/tools/index.js').then(t =>
+  t.analyzeComplexity({targetPath: 'src/', projectPath: process.cwd()})
+  .then(r => console.log(r.content[0].text))
+)"
+
+# Validate quality
+node -e "import('${corePathUrl}/node_modules/@su-record/vibe/dist/tools/index.js').then(t =>
+  t.validateCodeQuality({targetPath: 'src/', projectPath: process.cwd()})
+  .then(r => console.log(r.content[0].text))
+)"
+\`\`\`
+
+## Quality Metrics
+
+| Metric | Good | Warning | Critical |
+|--------|------|---------|----------|
+| Cyclomatic Complexity | ≤10 | 11-15 | >15 |
+| Function Length | ≤30 | 31-50 | >50 |
+| Nesting Depth | ≤3 | 4 | >4 |
+
+## Common Issues
+
+1. **High Complexity**: Extract helper functions
+2. **Long Functions**: Split by responsibility
+3. **Deep Nesting**: Use early returns
+4. **Tight Coupling**: Apply dependency injection
 `,
         },
         {
             id: 'session-management',
-            content: `---
-name: session-management
-description: "Context and session management across conversations"
-triggers: [session, context, memory, save, restore, continue]
-priority: 75
----
-# Session Management
-
-## Starting a Session
-
-\`\`\`bash
-# Auto-restore previous context
-node -e "import('${corePathUrl}/node_modules/@su-record/vibe/dist/tools/index.js').then(t =>
-  t.startSession({projectPath: process.cwd()})
-  .then(r => console.log(r.content[0].text))
-)"
-\`\`\`
-
-## Saving Context
-
-\`\`\`bash
-# Save important decisions
-node -e "import('${corePathUrl}/node_modules/@su-record/vibe/dist/tools/index.js').then(t =>
-  t.saveMemory({
-    key: 'decision-auth-method',
-    value: 'Using JWT with refresh tokens for auth',
-    category: 'architecture',
-    projectPath: process.cwd()
-  }).then(r => console.log(r.content[0].text))
-)"
-\`\`\`
-
-## Context Management
-
-At 70%+ context usage:
-1. Use \`saveMemory\` for important decisions
-2. Start new session with \`/new\`
-3. Previous context auto-restores
-
-## Slash Command
-
-\`\`\`
-/vibe.utils --continue
-\`\`\`
-
-Restores previous session context automatically.
+            content: `---
+name: session-management
+description: "Context and session management across conversations"
+triggers: [session, context, memory, save, restore, continue]
+priority: 75
+---
+# Session Management
+
+## Starting a Session
+
+\`\`\`bash
+# Auto-restore previous context
+node -e "import('${corePathUrl}/node_modules/@su-record/vibe/dist/tools/index.js').then(t =>
+  t.startSession({projectPath: process.cwd()})
+  .then(r => console.log(r.content[0].text))
+)"
+\`\`\`
+
+## Saving Context
+
+\`\`\`bash
+# Save important decisions
+node -e "import('${corePathUrl}/node_modules/@su-record/vibe/dist/tools/index.js').then(t =>
+  t.saveMemory({
+    key: 'decision-auth-method',
+    value: 'Using JWT with refresh tokens for auth',
+    category: 'architecture',
+    projectPath: process.cwd()
+  }).then(r => console.log(r.content[0].text))
+)"
+\`\`\`
+
+## Context Management
+
+At 70%+ context usage:
+1. Use \`saveMemory\` for important decisions
+2. Start new session with \`/new\`
+3. Previous context auto-restores
+
+## Slash Command
+
+\`\`\`
+/vibe.utils --continue
+\`\`\`
+
+Restores previous session context automatically.
 `,
         },
     ];

package/dist/infra/lib/UltraQA.js

@@ -92,60 +92,60 @@ export function shouldContinue(session) {
  * Generate architect diagnosis prompt
  */
 export function generateDiagnosisPrompt(result) {
-    return `
-## QA Failure Diagnosis Required
-
-**Cycle**: ${result.cycle}
-**Goal**: ${result.goal}
-**Command**: ${result.command}
-**Exit Code**: ${result.exitCode}
-
-### Output:
-\`\`\`
-${result.output.slice(0, 2000)}
-\`\`\`
-
-### Task:
-1. Identify the root cause of this failure
-2. Determine if it's a code issue, config issue, or environment issue
-3. Provide a specific fix recommendation
-
-Return JSON:
-\`\`\`json
-{
-  "rootCause": "description of root cause",
-  "category": "code|config|environment|dependency",
-  "fix": "specific fix to apply",
-  "files": ["list", "of", "files", "to", "modify"],
-  "confidence": "high|medium|low"
-}
-\`\`\`
+    return `
+## QA Failure Diagnosis Required
+
+**Cycle**: ${result.cycle}
+**Goal**: ${result.goal}
+**Command**: ${result.command}
+**Exit Code**: ${result.exitCode}
+
+### Output:
+\`\`\`
+${result.output.slice(0, 2000)}
+\`\`\`
+
+### Task:
+1. Identify the root cause of this failure
+2. Determine if it's a code issue, config issue, or environment issue
+3. Provide a specific fix recommendation
+
+Return JSON:
+\`\`\`json
+{
+  "rootCause": "description of root cause",
+  "category": "code|config|environment|dependency",
+  "fix": "specific fix to apply",
+  "files": ["list", "of", "files", "to", "modify"],
+  "confidence": "high|medium|low"
+}
+\`\`\`
 `.trim();
 }
 /**
  * Generate executor fix prompt
  */
 export function generateFixPrompt(diagnosis, result) {
-    return `
-## Apply Fix for QA Failure
-
-**Previous Diagnosis**:
-${diagnosis}
-
-**Failed Command**: ${result.command}
-**Cycle**: ${result.cycle}
-
-### Task:
-Apply the fix identified in the diagnosis. Make minimal changes to resolve the issue.
-
-### Rules:
-1. Only modify files mentioned in the diagnosis
-2. Make the smallest change that fixes the issue
-3. Do not refactor or improve unrelated code
-4. Run the verification command after fixing
-
-### After fixing, run:
-\`${result.command}\`
+    return `
+## Apply Fix for QA Failure
+
+**Previous Diagnosis**:
+${diagnosis}
+
+**Failed Command**: ${result.command}
+**Cycle**: ${result.cycle}
+
+### Task:
+Apply the fix identified in the diagnosis. Make minimal changes to resolve the issue.
+
+### Rules:
+1. Only modify files mentioned in the diagnosis
+2. Make the smallest change that fixes the issue
+3. Do not refactor or improve unrelated code
+4. Run the verification command after fixing
+
+### After fixing, run:
+\`${result.command}\`
 `.trim();
 }
 /**
@@ -157,28 +157,28 @@ export function generateArchitectureEscalationPrompt(session) {
     const failureSummary = recentFailures
         .map((c, i) => `  Attempt ${i + 1}: ${c.goal} - ${c.output.slice(0, 150)}`)
         .join('\n');
-    return `
-## ⚠️ 3-Fix Rule Triggered - Architecture Question Required
-
-**Same issue failed ${session.config.maxSameFailure}+ times.** This suggests an architectural problem, not a failed hypothesis.
-
-### Failure Pattern:
-${failureSummary}
-
-### Architecture Problem Indicators:
-- Each fix reveals new shared state/coupling issues in different places
-- Fixes require "massive refactoring" to implement
-- Each fix creates new symptoms elsewhere
-
-### Required Action:
-**STOP attempting more fixes.** Discuss with user before proceeding.
-
-### Questions for User:
-1. Is the current approach fundamentally sound?
-2. Are we persisting through sheer inertia?
-3. Should we refactor architecture vs. continue fixing symptoms?
-
-**Do NOT attempt Fix #${session.config.maxSameFailure + 1} without architectural discussion.**
+    return `
+## ⚠️ 3-Fix Rule Triggered - Architecture Question Required
+
+**Same issue failed ${session.config.maxSameFailure}+ times.** This suggests an architectural problem, not a failed hypothesis.
+
+### Failure Pattern:
+${failureSummary}
+
+### Architecture Problem Indicators:
+- Each fix reveals new shared state/coupling issues in different places
+- Fixes require "massive refactoring" to implement
+- Each fix creates new symptoms elsewhere
+
+### Required Action:
+**STOP attempting more fixes.** Discuss with user before proceeding.
+
+### Questions for User:
+1. Is the current approach fundamentally sound?
+2. Are we persisting through sheer inertia?
+3. Should we refactor architecture vs. continue fixing symptoms?
+
+**Do NOT attempt Fix #${session.config.maxSameFailure + 1} without architectural discussion.**
 `.trim();
 }
 /**
@@ -263,35 +263,35 @@ export function parseQAGoals(input) {
  * Create UltraQA workflow description
  */
 export function describeUltraQAWorkflow() {
-    return `
-## UltraQA Workflow
-
-5-cycle autonomous QA loop:
-
-\`\`\`
-┌─────────────────────────────────────────────┐
-│  ULTRAQA CYCLE                              │
-│                                             │
-│  1. Run verification (test/build/lint)      │
-│         ↓                                   │
-│  2. Check result                            │
-│         ↓                                   │
-│     ┌───┴───┐                               │
-│   PASS     FAIL                             │
-│     ↓        ↓                              │
-│   DONE    3. Architect diagnosis            │
-│              ↓                              │
-│           4. Executor fix                   │
-│              ↓                              │
-│           5. Repeat (max 5 cycles)          │
-└─────────────────────────────────────────────┘
-\`\`\`
-
-Exit conditions:
-- ✅ All goals pass (with evidence)
-- ⚠️ Same failure 3 times → Architecture Question (3-Fix Rule)
-- ❌ Max 5 cycles reached
-- ❌ Environment error
+    return `
+## UltraQA Workflow
+
+5-cycle autonomous QA loop:
+
+\`\`\`
+┌─────────────────────────────────────────────┐
+│  ULTRAQA CYCLE                              │
+│                                             │
+│  1. Run verification (test/build/lint)      │
+│         ↓                                   │
+│  2. Check result                            │
+│         ↓                                   │
+│     ┌───┴───┐                               │
+│   PASS     FAIL                             │
+│     ↓        ↓                              │
+│   DONE    3. Architect diagnosis            │
+│              ↓                              │
+│           4. Executor fix                   │
+│              ↓                              │
+│           5. Repeat (max 5 cycles)          │
+└─────────────────────────────────────────────┘
+\`\`\`
+
+Exit conditions:
+- ✅ All goals pass (with evidence)
+- ⚠️ Same failure 3 times → Architecture Question (3-Fix Rule)
+- ❌ Max 5 cycles reached
+- ❌ Environment error
 `.trim();
 }
 //# sourceMappingURL=UltraQA.js.map