From ace983730a9d32f1c4baca85a95ff490387173c0 Mon Sep 17 00:00:00 2001 From: Paul Gauthier Date: Tue, 20 Aug 2024 12:50:04 -0700 Subject: [PATCH] shell commands prompt --- aider/coders/editblock_prompts.py | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/aider/coders/editblock_prompts.py b/aider/coders/editblock_prompts.py index 7a2acdae9..48c344b05 100644 --- a/aider/coders/editblock_prompts.py +++ b/aider/coders/editblock_prompts.py @@ -17,11 +17,18 @@ Once you understand the request you MUST: 1. Decide if you need to propose *SEARCH/REPLACE* edits to any files that haven't been added to the chat. You can create new files without asking. But if you need to propose edits to existing files not already added to the chat, you *MUST* tell the user their full path names and ask them to *add the files to the chat*. End your reply and wait for their approval. You can keep asking if you then decide you need to edit more files. 2. Think step-by-step and explain the needed changes with a numbered list of short sentences. 3. Describe each change with a *SEARCH/REPLACE block* per the examples below. All changes to files must use this *SEARCH/REPLACE block* format. ONLY EVER RETURN CODE IN A *SEARCH/REPLACE BLOCK*! - -All changes to files must use the *SEARCH/REPLACE block* format. +4. *Briefly* and *concisely* suggest any shell commands the user might want to run, like: + - If you changed a self-contained html file, suggest an OS-appropriate command to open a browser to view it to see the updated content. + - If you changed a CLI program, suggest the command to run it to see the new behavior. + - If you added a test, suggest how to run it with the project's testing tool. + - Suggest OS-appropriate commands to delete or rename files/directories, or other file system operations. + - Suggest commands to install needed dependencies. + - Etc. Keep this info about the user's system in mind: {platform} + +All changes to files must use the *SEARCH/REPLACE block* format. """ example_messages = [