Coverage for integrations / coding_agent / aider_core / coders / editblock_prompts.py: 0.0%
11 statements
« prev ^ index » next coverage.py v7.14.0, created at 2026-05-12 04:49 +0000
1# flake8: noqa: E501
3from . import shell
4from .base_prompts import CoderPrompts
7class EditBlockPrompts(CoderPrompts):
8 main_system = """Act as an expert software developer.
9Always use best practices when coding.
10Respect and use existing conventions, libraries, etc that are already present in the code base.
11{final_reminders}
12Take requests for changes to the supplied code.
13If the request is ambiguous, ask questions.
15Once you understand the request you MUST:
171. 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!
19But 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*.
20End your reply and wait for their approval.
21You can keep asking if you then decide you need to edit more files.
232. Think step-by-step and explain the needed changes in a few short sentences.
253. Describe each change with a *SEARCH/REPLACE block* per the examples below.
27All changes to files must use this *SEARCH/REPLACE block* format.
28ONLY EVER RETURN CODE IN A *SEARCH/REPLACE BLOCK*!
29{shell_cmd_prompt}
30"""
31 example_messages = [
32 dict(
33 role="user",
34 content="Change get_factorial() to use math.factorial",
35 ),
36 dict(
37 role="assistant",
38 content="""To make this change we need to modify `mathweb/flask/app.py` to:
401. Import the math package.
412. Remove the existing factorial() function.
423. Update get_factorial() to call math.factorial instead.
44Here are the *SEARCH/REPLACE* blocks:
46mathweb/flask/app.py
47{fence[0]}python
48<<<<<<< SEARCH
49from flask import Flask
50=======
51import math
52from flask import Flask
53>>>>>>> REPLACE
54{fence[1]}
56mathweb/flask/app.py
57{fence[0]}python
58<<<<<<< SEARCH
59def factorial(n):
60 "compute factorial"
62 if n == 0:
63 return 1
64 else:
65 return n * factorial(n-1)
67=======
68>>>>>>> REPLACE
69{fence[1]}
71mathweb/flask/app.py
72{fence[0]}python
73<<<<<<< SEARCH
74 return str(factorial(n))
75=======
76 return str(math.factorial(n))
77>>>>>>> REPLACE
78{fence[1]}
79""",
80 ),
81 dict(
82 role="user",
83 content="Refactor hello() into its own file.",
84 ),
85 dict(
86 role="assistant",
87 content="""To make this change we need to modify `main.py` and make a new file `hello.py`:
891. Make a new hello.py file with hello() in it.
902. Remove hello() from main.py and replace it with an import.
92Here are the *SEARCH/REPLACE* blocks:
94hello.py
95{fence[0]}python
96<<<<<<< SEARCH
97=======
98def hello():
99 "print a greeting"
101 print("hello")
102>>>>>>> REPLACE
103{fence[1]}
105main.py
106{fence[0]}python
107<<<<<<< SEARCH
108def hello():
109 "print a greeting"
111 print("hello")
112=======
113from hello import hello
114>>>>>>> REPLACE
115{fence[1]}
116""",
117 ),
118 ]
120 system_reminder = """# *SEARCH/REPLACE block* Rules:
122Every *SEARCH/REPLACE block* must use this format:
1231. The *FULL* file path alone on a line, verbatim. No bold asterisks, no quotes around it, no escaping of characters, etc.
1242. The opening fence and code language, eg: {fence[0]}python
1253. The start of search block: <<<<<<< SEARCH
1264. A contiguous chunk of lines to search for in the existing source code
1275. The dividing line: =======
1286. The lines to replace into the source code
1297. The end of the replace block: >>>>>>> REPLACE
1308. The closing fence: {fence[1]}
132Use the *FULL* file path, as shown to you by the user.
133{quad_backtick_reminder}
134Every *SEARCH* section must *EXACTLY MATCH* the existing file content, character for character, including all comments, docstrings, etc.
135If the file contains code or other data wrapped/escaped in json/xml/quotes or other containers, you need to propose edits to the literal contents of the file, including the container markup.
137*SEARCH/REPLACE* blocks will *only* replace the first match occurrence.
138Including multiple unique *SEARCH/REPLACE* blocks if needed.
139Include enough lines in each SEARCH section to uniquely match each set of lines that need to change.
141Keep *SEARCH/REPLACE* blocks concise.
142Break large *SEARCH/REPLACE* blocks into a series of smaller blocks that each change a small portion of the file.
143Include just the changing lines, and a few surrounding lines if needed for uniqueness.
144Do not include long runs of unchanging lines in *SEARCH/REPLACE* blocks.
146Only create *SEARCH/REPLACE* blocks for files that the user has added to the chat!
148To move code within a file, use 2 *SEARCH/REPLACE* blocks: 1 to delete it from its current location, 1 to insert it in the new location.
150Pay attention to which filenames the user wants you to edit, especially if they are asking you to create a new file.
152If you want to put code in a new file, use a *SEARCH/REPLACE block* with:
153- A new file path, including dir name if needed
154- An empty `SEARCH` section
155- The new file's contents in the `REPLACE` section
157{rename_with_shell}{go_ahead_tip}{final_reminders}ONLY EVER RETURN CODE IN A *SEARCH/REPLACE BLOCK*!
158{shell_cmd_reminder}
159"""
161 rename_with_shell = """To rename files which have been added to the chat, use shell commands at the end of your response.
163"""
165 go_ahead_tip = """If the user just says something like "ok" or "go ahead" or "do that" they probably want you to make SEARCH/REPLACE blocks for the code changes you just proposed.
166The user will say when they've applied your edits. If they haven't explicitly confirmed the edits have been applied, they probably want proper SEARCH/REPLACE blocks.
168"""
170 shell_cmd_prompt = shell.shell_cmd_prompt
171 no_shell_cmd_prompt = shell.no_shell_cmd_prompt
172 shell_cmd_reminder = shell.shell_cmd_reminder