From 85a3111253da155fc9e88aebd11c6e8a77b5d487 Mon Sep 17 00:00:00 2001 From: YeonGyu-Kim Date: Fri, 19 Dec 2025 13:38:54 +0900 Subject: [PATCH] refactor(keyword-detector): relax analyze-mode recommendations for practical agent usage MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Reduce analyze-mode agent recommendations from aggressive (10+ agents, 3+ explore, 3+ librarian, 2+ general, 3+ oracle) to moderate (1-2 explore, 1-2 librarian, oracle only if complex) for simple requests like "살펴봐줘". Previous settings caused unnecessary agent spawning and token consumption for straightforward analysis tasks. New recommendation prioritizes context gathering with direct tools (Grep, AST-grep) for typical workflows, reserving oracle consultation for genuinely complex scenarios (architecture, multi-system, debugging after failures). 🤖 Generated with assistance of [OhMyOpenCode](https://github.com/code-yeongyu/oh-my-opencode) --- src/hooks/keyword-detector/constants.ts | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) diff --git a/src/hooks/keyword-detector/constants.ts b/src/hooks/keyword-detector/constants.ts index 6ca9796..f60de33 100644 --- a/src/hooks/keyword-detector/constants.ts +++ b/src/hooks/keyword-detector/constants.ts @@ -53,17 +53,16 @@ NEVER stop at first result - be exhaustive.`, pattern: /\b(analyze|analyse|investigate|examine|research|study|deep[\s-]?dive|inspect|audit|evaluate|assess|review|diagnose|scrutinize|dissect|debug|comprehend|interpret|breakdown|understand)\b|why\s+is|how\s+does|how\s+to|분석|조사|파악|연구|검토|진단|이해|설명|원인|이유|뜯어봐|따져봐|평가|해석|디버깅|디버그|어떻게|왜|살펴|分析|調査|解析|検討|研究|診断|理解|説明|検証|精査|究明|デバッグ|なぜ|どう|仕組み|调查|检查|剖析|深入|诊断|解释|调试|为什么|原理|搞清楚|弄明白|phân tích|điều tra|nghiên cứu|kiểm tra|xem xét|chẩn đoán|giải thích|tìm hiểu|gỡ lỗi|tại sao/i, message: `[analyze-mode] -DEEP ANALYSIS MODE. Execute in phases: +ANALYSIS MODE. Gather context before diving deep: -PHASE 1 - GATHER CONTEXT (10+ agents parallel): -- 3+ explore agents (codebase structure, patterns, implementations) -- 3+ librarian agents (official docs, best practices, examples) -- 2+ general agents (different analytical perspectives) +CONTEXT GATHERING (parallel): +- 1-2 explore agents (codebase patterns, implementations) +- 1-2 librarian agents (if external library involved) +- Direct tools: Grep, AST-grep, LSP for targeted searches -PHASE 2 - EXPERT CONSULTATION (after Phase 1): -- 3+ oracle agents in parallel with gathered context -- Each oracle: different angle (architecture, performance, edge cases) +IF COMPLEX (architecture, multi-system, debugging after 2+ failures): +- Consult oracle for strategic guidance -SYNTHESIZE: Cross-reference findings, identify consensus & contradictions.`, +SYNTHESIZE findings before proceeding.`, }, ]