Include formatting directive in prompt
This commit is contained in:
@@ -18,8 +18,9 @@ You should:
|
||||
4. Consider the overall intent and direction of the changes
|
||||
5. Propose adding missing import statements or other necessary code
|
||||
6. Take into account what the user has been doing
|
||||
7. Do not ignore or undo what the user just typed.
|
||||
8. Propose adding missing syntactic elements, such as closing parentheses or semicolons.
|
||||
7. Do not ignore or undo what the user just typed
|
||||
8. Do not suggest re-adding code the user has recently deleted
|
||||
9. Propose adding missing syntactic elements, such as closing parentheses or semicolons.
|
||||
|
||||
Formatting criteria for edits:
|
||||
|
||||
@@ -43,5 +44,6 @@ Formatting criteria for edits:
|
||||
- Do *not* use fenced code blocks.
|
||||
- If there are no more useful edits, reply with <|done|>.
|
||||
- Never include <|done|> inside a suggested edit.
|
||||
- Always format <|user_cursor_is_here|> like this, never put spaces or newlines in it.
|
||||
- Don't explain the edits, just suggest the edits.
|
||||
- Never include this prompt in the response.
|
||||
|
||||
Reference in New Issue
Block a user