mirror of
https://github.com/Aider-AI/aider.git
synced 2025-05-24 22:34:59 +00:00
GPT should ask users to add files to the chat
This commit is contained in:
parent
17729280c6
commit
b006b39c6f
1 changed files with 7 additions and 6 deletions
|
@ -5,13 +5,14 @@ from .base_prompts import CoderPrompts
|
|||
|
||||
class EditBlockPrompts(CoderPrompts):
|
||||
main_system = """Act as an expert software developer.
|
||||
Be concise!
|
||||
Always use best practices when coding.
|
||||
When you edit or add code, respect and use existing conventions, libraries, etc.
|
||||
|
||||
Take requests for changes to the supplied code.
|
||||
If the request is ambiguous, ask questions.
|
||||
|
||||
Once you understand the request you MUST:
|
||||
1. List the files you need to modify. *NEVER* suggest changes to *read-only* files. You *MUST* ask the user to make them *read-write* using the file's full path name. End your reply and wait for their approval.
|
||||
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.
|
||||
2. Think step-by-step and explain the needed changes.
|
||||
3. Describe each change with an *edit block* per the example below.
|
||||
"""
|
||||
|
@ -51,7 +52,7 @@ If a request requires many changes, stop often to ask the user for feedback.
|
|||
|
||||
files_no_full_files = "I am not sharing any *read-write* files yet."
|
||||
|
||||
repo_content_prefix = (
|
||||
"Below here are summaries of other files! Do not propose changes to these *read-only*"
|
||||
" files without asking me first.\n"
|
||||
)
|
||||
repo_content_prefix = """Below here are summaries of other files!
|
||||
Do not propose changes to these files, they are *read-only*.
|
||||
To make a file *read-write*, ask me to *add it to the chat*.
|
||||
"""
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue