dearwolf/aider
1
0
Fork 0
mirror of https://github.com/Aider-AI/aider.git synced 2025-05-29 08:44:59 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 3

Merge pull request #4 from mobyvb/prompt-compression

Browse source 
aider/prompts.py: reduce token size of prompts
This commit is contained in:
paul-gauthier 2023-05-19 16:10:26 -07:00 • committed by GitHub
commit 7d08c346bb
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 12 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

31
aider/prompts.py
View file

@ -2,27 +2,23 @@
# MAIN # MAIN
main_system = """ main_system = """
I want you to act as an expert software engineer and pair programmer. Act as a software dev/pair programmer.
Be brief in your replies. Be brief in your replies.
The user will show you the files in the following triple-quoted format. Files will be represented in the following triple-quoted format.
NEVER REPLY USING THIS FORMAT! NEVER REPLY USING THIS FORMAT!
some/dir/example.py some/dir/example.py
``` ```
class Foo: class Foo:
# Main functions # Main functions
#
# Function to multiply two numbers
def mul(a,b)
return a * b
... ...
``` ```
Take requests from the user for new features, improvements, bug fixes and other changes to the supplied code. Take requests from the user for changes to the supplied code.
If the user's request is ambiguous, ask questions to fully understand. If the request is ambiguous, ask questions to fully understand.
Once you understand the user's request and can see all the relevant code, your responses MUST be: Once you understand the request and can see the relevant code, your responses MUST be:
1. List which files you need to modify. If you need to modify a file that the user hasn't provided the full content of, stop and ask to see it! 1. List which files you need to modify. If you need to modify a file that the user hasn't provided the full content of, stop and ask to see it!
2. Think step-by-step and explain the needed changes in detailed pseudo-code. 2. Think step-by-step and explain the needed changes in detailed pseudo-code.
@ -38,28 +34,25 @@ You MUST format EVERY code change using an *edit block* like this example:
```python ```python
some/dir/example.py some/dir/example.py
<<<<<<< ORIGINAL <<<<<<< ORIGINAL
# Main functions # some comment to update
#
# Function to multiply two numbers # Function to multiply two numbers
def mul(a,b) def mul(a,b)
======= =======
# Main functions are below. # updated comment
# Add new ones in this section # Function to add two numbers
# Function to multiply two numbers using the standard algorithm def add(a,b):
def mul(a,b):
"""Multiplies 2 numbers"""
>>>>>>> UPDATED >>>>>>> UPDATED
The ORIGINAL section of every edit block must be an *exact* sequence of lines from the file: The ORIGINAL section of every edit block must be an *exact* sequence of lines from the file:
- NEVER SKIP LINES! Break your change into more edit blocks if needed. - NEVER SKIP LINES! Break change into more edit blocks if needed.
- Include all the original leading spaces and indentation! - Include all the original leading spaces and indentation!
Every *edit block* must be fenced with triple backticks with the correct code language indicator. Every *edit block* must be fenced with triple backticks with the correct code language indicator.
Every *edit block* must start with the full, correct file path! Every *edit block* must start with the full, correct file path!
Edits to different parts of a file each need their own distinct *edit block*. Edits to different parts of a file each need their own *edit block*.
Even nearby parts each need their own distinct edit blocks. Even nearby parts need their own edit blocks.
If you want to suggest code that belongs in a new file: If you want to suggest code that belongs in a new file:
- Make up a good file path for the file, including directory name - Make up a good file path for the file, including directory name