feat: rename execute_command tool, improve go prompt

lua/chatgpt_nvim/prompts.lua

@@ -244,16 +244,17 @@ local M = {
 
     You are helping me develop a large Go (Golang) project. Please keep the following points in mind when generating or explaining code:
 
-    1. **Go Modules**  
+    1. **Go Modules & Dependency Management**  
        - Use a single `go.mod` file at the project root for module management.  
        - Ensure you use proper import paths based on the module name.  
        - If you refer to internal packages, use relative paths consistent with the module’s structure (e.g., `moduleName/internal/packageA`).  
+       - **Use the execute_command Tool for Dependencies:** Instead of manually editing version numbers in `go.mod`, please utilize the `execute_command` tool to run dependency commands (such as `go get`) to automatically fetch and update dependencies. This ensures that the correct versions are used without relying on manually provided values.
 
     2. **Package Structure**  
        - Each folder should contain exactly one package.  
        - Avoid creating multiple packages in the same folder.  
        - Use descriptive folder names and keep package names concise, following Go naming conventions.  
-       - Do not duplicate function or type names across different files in the same folder/package.  
+       - Do not duplicate function or type names across different files in the same folder/package.
 
     3. **File & Folder Organization**  
        - Organize source code in a folder hierarchy that reflects functionality. For example:
@@ -271,24 +272,24 @@ local M = {
              └── shared/
          ```
        - Keep external-facing, reusable packages in `pkg/` and internal logic in `internal/`.  
-       - Place the `main()` function in the `cmd/<appname>` folder.  
+       - Place the `main()` function in the `cmd/<appname>` folder.
 
     4. **Coding Best Practices**  
        - Maintain idiomatic Go code (e.g., short function and variable names where obvious, PascalCase for exported symbols).  
        - Keep functions short, focused, and tested.  
        - Use Go’s standard library where possible before adding third-party dependencies.  
-       - When introducing new functions or types, ensure they are uniquely named to avoid collisions.  
+       - When introducing new functions or types, ensure they are uniquely named to avoid collisions.
 
     5. **Import Management**  
        - Ensure that every import is actually used in your code.  
        - Remove unused imports to keep your code clean and maintainable.  
        - Include all necessary imports for anything referenced in your code to avoid missing imports.  
-       - Verify that any introduced import paths match your module’s structure and do not cause naming conflicts.  
+       - Verify that any introduced import paths match your module’s structure and do not cause naming conflicts.
 
     6. **Output Format**  
        - Present any generated source code as well-organized Go files, respecting the single-package-per-folder rule.  
        - When explaining your reasoning, include any relevant architectural trade-offs and rationale (e.g., “I placed function X in package `my_lib` to keep the business logic separate from the command-line interface.”).  
-       - If you modify existing files, specify precisely which changes or additions you are making.  
+       - If you modify existing files, specify precisely which changes or additions you are making.
   ]],
   ["typo3"] = [[
     ### TYPO3 Development Guidelines
@@ -476,7 +477,7 @@ local M = {
          ```yaml
          project_name: "%PROJECT_NAME%"
          tools:
-           - tool: "executeCommand"
+           - tool: "execute_command"
              command: "shell command here"
          ```
 
@@ -490,7 +491,7 @@ local M = {
        - **Step 4: Make Changes**  
          Only after reading the file, proceed to use `edit_file` or `replace_in_file`.
        - **Step 5: Execute Commands if Needed**  
-         Use `executeCommand` as necessary, always within the YAML block.
+         Use `execute_command` as necessary, always within the YAML block.
        - **Step 6: Tell that request is complete**  
          Once all operations are done, confirm that the request is complete with a little summary.
        - **Step 7: Repeat other steps as necessary**
@@ -514,7 +515,7 @@ local M = {
         content: |
           # Full updated file content here
 
-      - tool: "executeCommand"
+      - tool: "execute_command"
         command: "ls -la"
     ```