refactor: optimize file search and update documentation for tool usage guidelines

Author: 239573049

Directory.Packages.props

@@ -1,7 +1,7 @@
 <Project>
   <PropertyGroup>
     <ManagePackageVersionsCentrally>true</ManagePackageVersionsCentrally>
-    <VersionSuffix>0</VersionSuffix>
+    <VersionSuffix>1</VersionSuffix>
     <TimeStamp>$([System.DateTime]::UtcNow.ToString("yyyyMMdd"))</TimeStamp>
     <Version>0.9.$(VersionSuffix)</Version>
     <!-- 项目信息 -->

src/KoalaWiki/Git/GitService.cs

@@ -22,7 +22,7 @@ public static (string localPath, string organization) GetRepositoryPath(string r
 
 
         // 对于 GitLab，最后一个段是仓库名，前面的都是组织/子组织  
-        repositoryName = segments[segments.Length - 1].Trim('/').Replace(".git", "");
+        repositoryName = segments[^1].Trim('/').Replace(".git", "");
 
         // 组织名包含所有中间路径，用下划线连接以避免路径冲突  
         var orgParts = new List<string>();

src/KoalaWiki/KernelFactory.cs

@@ -104,11 +104,8 @@ public static Kernel GetKernel(string chatEndpoint,
         var fileFunction = new FileTool(gitPath, files);
         kernelBuilder.Plugins.AddFromObject(fileFunction, "file");
 
-        if (DocumentOptions.EnableAgentTool)
-        {
-            kernelBuilder.Plugins.AddFromType<AgentTool>();
-            activity?.SetTag("plugins.agent_tool", "loaded");
-        }
+        kernelBuilder.Plugins.AddFromType<AgentTool>();
+        activity?.SetTag("plugins.agent_tool", "loaded");
 
         activity?.SetTag("plugins.file_function", "loaded");
 

src/KoalaWiki/KoalaWarehouse/GenerateThinkCatalogue/GenerateThinkCatalogueService.Prompt.cs

@@ -5,56 +5,17 @@ namespace KoalaWiki.KoalaWarehouse.GenerateThinkCatalogue;
 public partial class GenerateThinkCatalogueService
 {
     public static async Task<string> GenerateThinkCataloguePromptAsync(ClassifyType? classifyType,
-        string catalogue, int attemptNumber)
+        string catalogue)
     {
         var projectType = GetProjectTypeDescription(classifyType);
         var basePrompt = await PromptContext.Warehouse(nameof(PromptConstant.Warehouse.AnalyzeCatalogue),
             new KernelArguments()
             {
                 ["code_files"] = catalogue,
-                ["projectType"] = projectType,
-                ["language"] = Prompt.Language
+                ["projectType"] = projectType
             }, OpenAIOptions.AnalysisModel);
 
-        var toolUsage = """
-                        ## Catalogue Tool Usage Guidelines
-                        
-                        **PARALLEL READ OPERATIONS**
-                        - MANDATORY: Always perform PARALLEL File.Read calls — batch multiple files in a SINGLE message for maximum efficiency
-                        - CRITICAL: Read MULTIPLE files simultaneously in one operation
-                        - PROHIBITED: Sequential one-by-one file reads (inefficient and wastes context capacity)
-                        
-                        **EDITING OPERATION LIMITS**
-                        - HARD LIMIT: Maximum of 3 editing operations total (Catalogue.MultiEdit only)
-                        - PRIORITY: Maximize each Catalogue.MultiEdit operation by bundling ALL related changes across multiple files
-                        - STRATEGIC PLANNING: Consolidate all modifications into minimal MultiEdit operations to stay within the limit
-                        - Use Catalogue.Write **only once** for initial creation or full rebuild (counts as initial structure creation, not part of the 3 edits)
-                        - Always verify content before further changes using Catalogue.Read (Reads do NOT count toward limit)
-                        
-                        **CRITICAL MULTIEDIT BEST PRACTICES**
-                        - MAXIMIZE EFFICIENCY: Each MultiEdit should target multiple distinct sections across files
-                        - AVOID CONFLICTS: Never edit overlapping or identical content regions within the same MultiEdit operation
-                        - UNIQUE TARGETS: Ensure each edit instruction addresses a completely different section or file
-                        - BATCH STRATEGY: Group all necessary changes by proximity and relevance, but maintain clear separation between edit targets
-                        
-                        **RECOMMENDED EDITING SEQUENCE**
-                        1. Initial creation → Catalogue.Write (one-time full structure creation)
-                        2. Bulk refinements → Catalogue.MultiEdit with maximum parallel changes (counts toward 3-operation limit)
-                        3. Validation → Use Catalogue.Read after each MultiEdit to verify success before next operation
-                        4. Final adjustments → Remaining MultiEdit operations for any missed changes
-                        """;
-
-        // Attempt-based enhancement focusing on specific quality improvements
-        var enhancementLevel = Math.Min(attemptNumber, 3);
-        var enhancement = enhancementLevel switch
-        {
-            0 => "\n\nATTEMPT 1 FOCUS: Prioritize thorough code analysis and solid JSON foundation.",
-            1 => "\n\nATTEMPT 2 FOCUS: Emphasize structural depth and component relationships.",
-            2 => "\n\nATTEMPT 3 FOCUS: Optimize prompt specificity and actionable guidance.",
-            _ => "\n\nFINAL ATTEMPT: Address any remaining gaps and ensure completeness."
-        };
-
-        return toolUsage + basePrompt + enhancement;
+        return basePrompt;
     }
 
 
@@ -145,4 +106,4 @@ private static string GetProjectTypeDescription(ClassifyType? classifyType)
                Provide thorough analysis that serves both newcomers seeking understanding and experienced developers requiring implementation details.
                """;
     }
-}
+}

src/KoalaWiki/KoalaWarehouse/GenerateThinkCatalogue/GenerateThinkCatalogueService.cs

@@ -41,7 +41,7 @@ private enum ErrorType
             try
             {
                 var result =
-                    await ExecuteSingleAttempt(path, catalogue, warehouse, classify, retryCount);
+                    await ExecuteSingleAttempt(path, catalogue, classify, retryCount);
 
                 if (result != null)
                 {
@@ -97,11 +97,10 @@ private enum ErrorType
     }
 
     private static async Task<DocumentResultCatalogue?> ExecuteSingleAttempt(
-        string path, string catalogue,
-        Warehouse warehouse, ClassifyType? classify, int attemptNumber)
+        string path, string catalogue, ClassifyType? classify, int attemptNumber)
     {
         // 根据尝试次数调整提示词策略
-        var enhancedPrompt = await GenerateThinkCataloguePromptAsync(classify, catalogue, attemptNumber);
+        var enhancedPrompt = await GenerateThinkCataloguePromptAsync(classify, catalogue);
 
         var history = new ChatHistory();
 
@@ -113,10 +112,43 @@ private enum ErrorType
             new TextContent(
                 $"""
                  <system-reminder>
-                 **CRITICAL FIRST STEP: You MUST begin every research task by calling the 'think' tool to analyze the query complexity. This is mandatory and must be the very first action you take, regardless of the query type or complexity.**
+                 <catalog_tool_usage_guidelines>
+                 **PARALLEL READ OPERATIONS**
+                 - MANDATORY: Always perform PARALLEL File.Read calls — batch multiple files in a SINGLE message for maximum efficiency
+                 - CRITICAL: Read MULTIPLE files simultaneously in one operation
+                 - PROHIBITED: Sequential one-by-one file reads (inefficient and wastes context capacity)
+                 
+                 **EDITING OPERATION LIMITS**
+                 - HARD LIMIT: Maximum of 3 editing operations total (catalog.MultiEdit only)
+                 - PRIORITY: Maximize each catalog.MultiEdit operation by bundling ALL related changes across multiple files
+                 - STRATEGIC PLANNING: Consolidate all modifications into minimal MultiEdit operations to stay within the limit
+                 - Use catalog.Write **only once** for initial creation or full rebuild (counts as initial structure creation, not part of the 3 edits)
+                 - Always verify content before further changes using catalog.Read (Reads do NOT count toward limit)
+                 
+                 **CRITICAL MULTIEDIT BEST PRACTICES**
+                 - MAXIMIZE EFFICIENCY: Each MultiEdit should target multiple distinct sections across files
+                 - AVOID CONFLICTS: Never edit overlapping or identical content regions within the same MultiEdit operation
+                 - UNIQUE TARGETS: Ensure each edit instruction addresses a completely different section or file
+                 - BATCH STRATEGY: Group all necessary changes by proximity and relevance, but maintain clear separation between edit targets
+                 
+                 **RECOMMENDED EDITING SEQUENCE**
+                 1. catalog.Write (one-time full structure creation)
+                 2. catalog.MultiEdit with maximum parallel changes (counts toward 3-operation limit)
+                 3. Use catalog.Read after each MultiEdit to verify success before next operation
+                 4. Remaining MultiEdit operations for any missed changes
+                 </catalog_tool_usage_guidelines>
+                 
+                 
+                 ## Execution steps requirements:
+                 1. Before performing any other operations, you must first invoke the 'agent-think' tool to plan the analytical steps. This is a necessary step for completing each research task.
+                 2. Then, the code structure provided in the code_file must be utilized by calling file.Read to read the code for in-depth analysis, and then use catalog.Write to write the results of the analysis into the catalog directory.
+                 3. If necessary, some parts that need to be optimized can be edited through catalog.MultiEdit.
+                 
                  For maximum efficiency, whenever you need to perform multiple independent operations, invoke all relevant tools simultaneously rather than sequentially.
-                 Note: The repository's directory structure has been provided in <code_files>. Please utilize the provided structure directly for file navigation and reading operations, rather than relying on glob patterns or filesystem traversal methods.
+                 The repository's directory structure has been provided in <code_files>. Please utilize the provided structure directly for file navigation and reading operations, rather than relying on glob patterns or filesystem traversal methods.
+                 
                  {Prompt.Language}
+                 
                  </system-reminder>
                  """),
             new TextContent(Prompt.Language)
@@ -127,7 +159,7 @@ private enum ErrorType
         var catalogueTool = new CatalogueFunction();
         var analysisModel = KernelFactory.GetKernel(OpenAIOptions.Endpoint,
             OpenAIOptions.ChatApiKey, path, OpenAIOptions.AnalysisModel, false, null,
-            builder => { builder.Plugins.AddFromObject(catalogueTool, "Catalogue"); });
+            builder => { builder.Plugins.AddFromObject(catalogueTool, "catalog"); });
 
         var chat = analysisModel.Services.GetService<IChatCompletionService>();
         if (chat == null)
@@ -146,7 +178,7 @@ private enum ErrorType
 
         var inputTokenCount = 0;
         var outputTokenCount = 0;
-        
+
         retry:
         // 流式获取响应
         await foreach (var item in chat.GetStreamingChatMessageContentsAsync(history, settings, analysisModel))
@@ -196,6 +228,7 @@ private static async Task RefineResponse(ChatHistory history, IChatCompletionSer
                                                   • enrich each section's 'prompt' with actionable guidance (scope, code areas, outputs)
                                                 - Prefer localized edits; only use Catalogue.Write for a complete rewrite if necessary.
                                                 - Never print JSON in chat; use tools exclusively.
+                                                - Start by editing some parts that need optimization through catalog.MultiEdit.
                                             """;
 
             history.AddUserMessage(refinementPrompt);