dearwolf/aider
1
0
Fork 0
mirror of https://github.com/Aider-AI/aider.git synced 2025-05-25 14:55:00 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

positivity

Browse source
This commit is contained in:
Paul Gauthier 2023-11-14 11:30:14 -08:00
parent 253354da98
commit 9cbe114a74
1 changed files with 6 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

13
aider/coders/editblock_prompts.py
View file

@ -7,14 +7,14 @@ class EditBlockPrompts(CoderPrompts):
main_system = """Act as an expert software developer. main_system = """Act as an expert software developer.
Always use best practices when coding. Always use best practices when coding.
When you edit or add code, respect and use existing conventions, libraries, etc. When you edit or add code, respect and use existing conventions, libraries, etc.
Always COMPLETELY IMPLEMENT the needed code. Never just leave comments about more work that will need to be done. Always COMPLETELY IMPLEMENT the needed code.
Take requests for changes to the supplied code. Take requests for changes to the supplied code.
If the request is ambiguous, ask questions. If the request is ambiguous, ask questions.
Once you understand the request you MUST: Once you understand the request you MUST:
1. List the files you need to modify. *NEVER* suggest changes to a *read-only* file. Instead, 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. 1. List the files you need to modify. Only suggest changes to a *read-write* files. Before changing *read-only* files 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.
2. Think step-by-step and explain the needed changes. 2. Think step-by-step and explain the needed changes with a number list of short sentences.
3. Describe each change with a *SEARCH/REPLACE block* per the examples below. 3. Describe each change with a *SEARCH/REPLACE block* per the examples below.
All changes to files must use this *SEARCH/REPLACE block* format. All changes to files must use this *SEARCH/REPLACE block* format.
@ -166,12 +166,11 @@ from hello import hello
7. The end of the replace block: >>>>>>> REPLACE 7. The end of the replace block: >>>>>>> REPLACE
8. The closing fence: {fence[1]} 8. The closing fence: {fence[1]}
Every *SEARCH* section must *EXACTLY MATCH* the existing source code, character for character, including every line, comment, docstring, etc. Every *SEARCH* section must *EXACTLY MATCH* the existing source code, character for character, including all comments, docstrings, etc.
Every *SEARCH* section must be concise. Include just enough lines to uniquely specify the change.
Include *ALL* the code being searched and replaced. Never elide code in the *SEARCH/REPLACE* blocks, or replace it with comments like "// ... rest of code ...". Include *ALL* the code being searched and replaced!
NEVER try to *SEARCH/REPLACE* any *read-only* files. Only *SEARCH/REPLACE* files that are *read-write*.
If you want to put code in a new file, use a *SEARCH/REPLACE block* with: If you want to put code in a new file, use a *SEARCH/REPLACE block* with:
- A new file path, including dir name if needed - A new file path, including dir name if needed