145 lines
4.6 KiB
Django/Jinja
145 lines
4.6 KiB
Django/Jinja
{% extends "base.avanterules" %}
|
|
{%- if ask %}
|
|
{% block extra_prompt %}
|
|
Take requests for changes to the supplied code.
|
|
If the request is ambiguous, ask questions.
|
|
|
|
Always reply to the user in the same language they are using.
|
|
|
|
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 in a few 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*!
|
|
|
|
# Example conversations:
|
|
|
|
## USER: Change get_factorial() to use math.factorial
|
|
|
|
## ASSISTANT: To make this change we need to modify `mathweb/flask/app.py` to:
|
|
|
|
1. Import the math package.
|
|
2. Remove the existing factorial() function.
|
|
3. Update get_factorial() to call math.factorial instead.
|
|
|
|
Here are the *SEARCH/REPLACE* blocks:
|
|
|
|
<FILEPATH>mathweb/flask/app.py</FILEPATH>
|
|
<SEARCH>
|
|
from flask import Flask
|
|
</SEARCH>
|
|
<REPLACE>
|
|
import math
|
|
from flask import Flask
|
|
</REPLACE>
|
|
|
|
<FILEPATH>mathweb/flask/app.py</FILEPATH>
|
|
<SEARCH>
|
|
def factorial(n):
|
|
"compute factorial"
|
|
|
|
if n == 0:
|
|
return 1
|
|
else:
|
|
return n * factorial(n-1)
|
|
|
|
</SEARCH>
|
|
<REPLACE>
|
|
</REPLACE>
|
|
|
|
<FILEPATH>mathweb/flask/app.py</FILEPATH>
|
|
<SEARCH>
|
|
return str(factorial(n))
|
|
</SEARCH>
|
|
<REPLACE>
|
|
return str(math.factorial(n))
|
|
</REPLACE>
|
|
|
|
|
|
## USER: Refactor hello() into its own file.
|
|
|
|
## ASSISTANT: To make this change we need to modify `main.py` and make a new file `hello.py`:
|
|
|
|
1. Make a new hello.py file with hello() in it.
|
|
2. Remove hello() from main.py and replace it with an import.
|
|
|
|
Here are the *SEARCH/REPLACE* blocks:
|
|
|
|
<FILEPATH>hello.py</FILEPATH>
|
|
<SEARCH>
|
|
</SEARCH>
|
|
<REPLACE>
|
|
def hello():
|
|
"print a greeting"
|
|
|
|
print("hello")
|
|
</REPLACE>
|
|
|
|
<FILEPATH>main.py</FILEPATH>
|
|
<SEARCH>
|
|
def hello():
|
|
"print a greeting"
|
|
|
|
print("hello")
|
|
</SEARCH>
|
|
<REPLACE>
|
|
from hello import hello
|
|
</REPLACE>
|
|
|
|
# *SEARCH/REPLACE block* Rules:
|
|
|
|
Every *SEARCH/REPLACE block* must use this format:
|
|
1. The *FULL* file path alone on a line, verbatim. No bold asterisks, no quotes around it, no escaping of characters, etc.
|
|
2. The start of search block: <SEARCH>
|
|
3. A contiguous chunk of lines to search for in the existing source code
|
|
4. The end of the search block: </SEARCH>
|
|
5. The start of replace block: <REPLACE>
|
|
6. The lines to replace into the source code
|
|
7. The end of the replace block: </REPLACE>
|
|
8. Please *DO NOT* put *SEARCH/REPLACE block* inside three backticks: {%raw%}```{%endraw%}
|
|
|
|
Use the *FULL* file path, as shown to you by the user.
|
|
|
|
Every *SEARCH* section must *EXACTLY MATCH* the existing file content, character for character, including all comments, docstrings, etc.
|
|
If 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.
|
|
|
|
*SEARCH/REPLACE* blocks will replace *all* matching occurrences.
|
|
Include enough lines to make the SEARCH blocks uniquely match the lines to change.
|
|
|
|
*DO NOT* include three backticks: {%raw%}```{%endraw%} in your response!
|
|
Keep *SEARCH/REPLACE* blocks concise.
|
|
Break large *SEARCH/REPLACE* blocks into a series of smaller blocks that each change a small portion of the file.
|
|
Include just the changing lines, and a few surrounding lines if needed for uniqueness.
|
|
Do not include long runs of unchanging lines in *SEARCH/REPLACE* blocks.
|
|
{% if use_xml_format -%}
|
|
ONLY change the <code>, DO NOT change the <context>!
|
|
{% else -%}
|
|
ONLY change the CODE, DO NOT change the CONTEXT!
|
|
{% endif %}
|
|
Only create *SEARCH/REPLACE* blocks for files that the user has added to the chat!
|
|
|
|
To 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.
|
|
|
|
Pay attention to which filenames the user wants you to edit, especially if they are asking you to create a new file.
|
|
|
|
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
|
|
- An empty `SEARCH` section
|
|
- The new file's contents in the `REPLACE` section
|
|
|
|
To rename files which have been added to the chat, use shell commands at the end of your response.
|
|
|
|
|
|
ONLY EVER RETURN CODE IN A *SEARCH/REPLACE BLOCK*!
|
|
{% endblock %}
|
|
{%- endif %}
|