@polka-codes/cli-shared 0.9.5 → 0.9.6

package/dist/index.js

@@ -27293,7 +27293,7 @@ var handler8 = async (provider, args) => {
       if (isEmpty) {
         resp.push(`<read_file_file_content path="${path}" is_empty="true" />`);
       } else {
-        resp.push(`<read_file_file_conten path="${path}">${fileContent}</read_file_file_content>`);
+        resp.push(`<read_file_file_content path="${path}">${fileContent}</read_file_file_content>`);
       }
     }
   }
@@ -27593,8 +27593,15 @@ var handler11 = async (provider, args) => {
       message: "Not possible to replace in file. Abort."
     };
   }
+  const parsed = toolInfo11.parameters.safeParse(args);
+  if (!parsed.success) {
+    return {
+      type: "Invalid" /* Invalid */,
+      message: `Invalid arguments for replace_in_file: ${parsed.error.message}`
+    };
+  }
+  const { path, diff } = parsed.data;
   try {
-    const { path, diff } = toolInfo11.parameters.parse(args);
     const fileContent = await provider.readFile(path, false);
     if (fileContent == null) {
       return {
@@ -27672,8 +27679,15 @@ var handler12 = async (provider, args) => {
       message: "Not possible to search files. Abort."
     };
   }
+  const parsed = toolInfo12.parameters.safeParse(args);
+  if (!parsed.success) {
+    return {
+      type: "Invalid" /* Invalid */,
+      message: `Invalid arguments for search_files: ${parsed.error.message}`
+    };
+  }
+  const { path, regex, filePattern } = parsed.data;
   try {
-    const { path, regex, filePattern } = toolInfo12.parameters.parse(args);
     const files = await provider.searchFiles(path, regex, filePattern ?? "*");
     return {
       type: "Reply" /* Reply */,
@@ -27688,8 +27702,8 @@ ${files.join(`
     };
   } catch (error40) {
     return {
-      type: "Invalid" /* Invalid */,
-      message: `Invalid arguments for search_files: ${error40}`
+      type: "Error" /* Error */,
+      message: `Error searching files: ${error40}`
     };
   }
 };
@@ -51549,6 +51563,196 @@ var codeFixerAgentInfo = {
     "Tracking and reporting unfixed issues"
   ]
 };
+
+// ../core/src/Agent/CoderAgent/prompts.ts
+var basePrompt2 = "You are a highly skilled software engineer with extensive knowledge in many programming languages, frameworks, design patterns, and best practices.";
+var editingFilesPrompt = (toolNamePrefix) => `
+====
+
+EDITING FILES
+
+You have two file-manipulation tools: **${toolNamePrefix}write_to_file** (full overwrite) and **${toolNamePrefix}replace_in_file** (targeted anchor-based edits). Choose the smallest safe operation for every change.
+
+# ${toolNamePrefix}write_to_file
+
+## Purpose
+
+- Create a new file, or overwrite the entire contents of an existing file.
+
+## When to Use
+
+- Initial file creation, such as when scaffolding a new project.
+- Overwriting large boilerplate files where you want to replace the entire content at once.
+- When the complexity or number of changes would make ${toolNamePrefix}replace_in_file unwieldy or error-prone.
+- When you need to completely restructure a file's content or change its fundamental organization.
+
+## Important Considerations
+
+- Using ${toolNamePrefix}write_to_file requires providing the file's complete final content.
+- If you only need to make small changes to an existing file, consider using ${toolNamePrefix}replace_in_file instead to avoid unnecessarily rewriting the entire file.
+- While ${toolNamePrefix}write_to_file should not be your default choice, don't hesitate to use it when the situation truly calls for it.
+
+# ${toolNamePrefix}replace_in_file
+
+## Purpose
+
+- Make targeted edits to specific parts of an existing file without overwriting the entire file.
+
+## When to Use
+
+- Small, localized changes like updating a few lines, function implementations, changing variable names, modifying a section of text, etc.
+- Targeted improvements where only specific portions of the file's content needs to be altered.
+- Especially useful for long files where much of the file will remain unchanged.
+
+## Advantages
+
+- More efficient for minor edits, since you don't need to supply the entire file content.
+- Reduces the chance of errors that can occur when overwriting large files.
+
+# Choosing the Appropriate Tool
+
+- **Default to ${toolNamePrefix}replace_in_file** for most changes. It keeps diffs small and reduces risk.
+- **Use ${toolNamePrefix}write_to_file** when:
+  - Creating new files
+  - The changes are so extensive that using ${toolNamePrefix}replace_in_file would be more complex or risky
+  - You need to completely reorganize or restructure a file
+  - The file is relatively small and the changes affect most of its content
+  - You're generating boilerplate or template files
+
+# Workflow Tips
+
+1. Before editing, assess the scope of your changes and decide which tool to use.
+2. For targeted edits, apply ${toolNamePrefix}replace_in_file with carefully crafted before/after text anchors. If you need multiple changes, you can stack multiple operations within a single ${toolNamePrefix}replace_in_file call.
+3. For major overhauls or initial file creation, rely on ${toolNamePrefix}write_to_file.
+4. Once the file has been edited with either ${toolNamePrefix}write_to_file or ${toolNamePrefix}replace_in_file, the system will provide you with the final state of the modified file. Use this updated content as the reference point for any subsequent operations, since it reflects any auto-formatting or user-applied changes.
+
+Picking the right tool keeps edits minimal, safe, and easy to review.
+`;
+var rules = (toolNamePrefix) => `
+====
+
+RULES
+
+- Work only with relative paths; you may \`cd\` into child directories but never use \`cd ..\`, root, or absolute paths.
+- When generating code, tests, or other comment-capable files, prepend a comment describing the file's purpose plus “generated by polka.codes”.
+  For text files (e.g. README.md), append a footer with the same notice.
+- Never describe what changed inside code comments; comments must focus on purpose or usage only.
+- Before using ${toolNamePrefix}execute_command, consider SYSTEM INFORMATION to ensure commands suit the user's OS. If a command must run in a subdirectory, prepend a single \`cd childDir &&\` segment.
+- Use ${toolNamePrefix}search_files for broad analysis, then ${toolNamePrefix}read_file to inspect context, and finally ${toolNamePrefix}replace_in_file or ${toolNamePrefix}write_to_file to modify.
+- Prefer ${toolNamePrefix}replace_in_file for focused edits; choose ${toolNamePrefix}write_to_file for new files or complete rewrites.
+- When creating a new file, look for existing files with similar content or patterns; if found, read them and use their structure or conventions as a reference.
+- Use before/after text anchors in ${toolNamePrefix}replace_in_file to target changes. If multiple operations are needed, list them in file order.
+- Do not guess unseen content. Read existing files first unless creating new ones.
+- Follow existing style, lint, and naming conventions. Ensure all changes compile and pass tests where applicable.
+- ALWAYS wait for the user's confirmation after each tool call before starting the next step.
+- The agent must never invoke more than 5 tools in a single response.
+- Do not end ${toolNamePrefix}attempt_completion output with questions or conversational prompts.
+- Avoid filler words like “Great”, “Certainly”, “Okay”, “Sure” at the start of responses; be direct and technical.
+- Keep inline documentation current as you edit.
+`;
+var objectives = (toolNamePrefix) => `
+====
+
+OBJECTIVE
+
+You solve the user's task by working in small, verifiable steps.
+
+1. **Plan** - Parse the task, list clear goals, and order them logically.
+2. **Think** - Wrap private reasoning in <thinking></thinking>.
+   • Review project context.
+   • Select the single best tool for the next goal.
+   • Ensure every required parameter is available or can be inferred.
+3. **Act** - Invoke one tool per step. Wait for the system's response (and user confirmation where required) before continuing.
+4. **Iterate** - Repeat Plan → Think → Act until all goals are complete.
+5. **Complete** - Use ${toolNamePrefix}attempt_completion to deliver the final result. Do not invite further discussion unless the user explicitly requests changes.
+`;
+var fullSystemPrompt4 = (info, tools, toolNamePrefix, instructions, scripts, useNativeTool) => `
+${basePrompt2}
+${useNativeTool ? "" : toolUsePrompt(tools, toolNamePrefix)}
+${editingFilesPrompt(toolNamePrefix)}
+${capabilities(toolNamePrefix)}
+${rules(toolNamePrefix)}
+${objectives(toolNamePrefix)}
+${systemInformation(info)}
+${customInstructions(instructions)}
+${customScripts(scripts)}
+`;
+
+// ../core/src/Agent/CoderAgent/index.ts
+class CoderAgent extends AgentBase {
+  constructor(options) {
+    const combinedTools = [...options.additionalTools ?? [], ...Object.values(exports_allTools)];
+    const tools = getAvailableTools({
+      provider: options.provider,
+      allTools: combinedTools,
+      hasAgent: (options.agents?.length ?? 0) > 0,
+      permissionLevel: 3 /* Arbitrary */,
+      interactive: true
+    });
+    const toolNamePrefix = options.toolFormat === "native" ? "" : "tool_";
+    const systemPrompt = fullSystemPrompt4({
+      os: options.os
+    }, tools, toolNamePrefix, options.customInstructions ?? [], options.scripts ?? {}, options.toolFormat === "native");
+    super(coderAgentInfo.name, options.ai, {
+      systemPrompt,
+      tools,
+      toolNamePrefix,
+      provider: options.provider,
+      interactive: options.interactive,
+      agents: options.agents,
+      scripts: options.scripts,
+      callback: options.callback,
+      policies: options.policies,
+      toolFormat: options.toolFormat,
+      parameters: options.parameters ?? {},
+      usageMeter: options.usageMeter ?? new UsageMeter
+    });
+  }
+  async#runScript(scriptName, shouldReplyWithError) {
+    const executeCommand = this.config.provider.executeCommand;
+    if (!executeCommand) {
+      return;
+    }
+    const script = this.config.scripts?.[scriptName];
+    const command = typeof script === "string" ? script : script?.command;
+    if (command) {
+      try {
+        const { exitCode, stdout, stderr } = await executeCommand(command, false);
+        if (exitCode !== 0 && shouldReplyWithError) {
+          return {
+            type: "Reply" /* Reply */,
+            message: responsePrompts.commandResult(command, exitCode, stdout, stderr)
+          };
+        }
+      } catch (error81) {
+        console.warn(`Failed to run ${scriptName} using command: ${command}`, error81);
+      }
+    }
+  }
+  async onBeforeInvokeTool(name17, _args) {
+    if (name17 !== attemptCompletion_default.name) {
+      return;
+    }
+    await this.#runScript("format", false);
+    const checkResult = await this.#runScript("check", true);
+    if (checkResult) {
+      return checkResult;
+    }
+    const testResult = await this.#runScript("test", true);
+    if (testResult) {
+      return testResult;
+    }
+  }
+}
+var coderAgentInfo = {
+  name: "coder",
+  responsibilities: [
+    "Editing and refactoring existing code.",
+    "Creating new features or modules.",
+    "Running tests and analyzing test results.",
+    "Maintaining coding standards, lint rules, and general code quality."
+  ]
+};
 // ../core/src/Agent/MultiAgent.ts
 class MultiAgent {
   #config;
@@ -51894,10 +52098,18 @@ Example Output:
 <tool_output>
 <tool_output_pr_title>Refactor Order Validation and Remove Debug Logs</tool_output_pr_title>
 <tool_output_pr_description>
-closes #123
+Closes #123
+
+**Context**:
+- Implementing changes for issue #123 - Focus on clean code and maintainability
 
-This PR removes unnecessary debug print statements and updates order validation
-to use the new validate_and_process method for improved maintainability.
+**Summary of Changes**:
+- Refactored order validation logic to use a new \`validate_and_process\` method.
+- Removed debug print statements from \`user_service.py\`.
+
+**Highlights of Changed Code**:
+- \`order_service.py\`: Replaced direct call to \`process_order\` with \`validate_and_process\`.
+- \`user_service.py\`: Removed \`print("Debug info")\`.
 </tool_output_pr_description>
 </tool_output>
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@polka-codes/cli-shared",
-  "version": "0.9.5",
+  "version": "0.9.6",
   "license": "AGPL-3.0",
   "author": "github@polka.codes",
   "type": "module",