From 19a5dc658ea1ba5383f04a166146d9d74ed6f227 Mon Sep 17 00:00:00 2001 From: abhishekbhakat Date: Thu, 13 Mar 2025 08:49:46 +0000 Subject: [PATCH] Fix formatting instructions in XML documentation for clarity and correct spelling --- resources/xml_formatting_instructions.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/resources/xml_formatting_instructions.xml b/resources/xml_formatting_instructions.xml index ca76f9a..0b928a2 100644 --- a/resources/xml_formatting_instructions.xml +++ b/resources/xml_formatting_instructions.xml @@ -16,7 +16,7 @@ Avoid placeholders like `...` or `// existing code here`. Provide complete lines 3. **modify** (search/replace) – For partial edits with + . 4. **delete** – Remove a file entirely (empty ). -### **Format to Follow for Repo Prompt's Diff Protocol** +### **Format to Follow for Diff Protocol** Describe your approach or reasoning here. @@ -288,7 +288,7 @@ Remove an obsolete file. 5. You can always **create** new files and **delete** existing files. Provide full code for create, and empty content for delete. Avoid creating files you know exist already. 6. If a file tree is provided, place your files logically within that structure. Respect the user’s relative or absolute paths. 7. Wrap your final output in ```XML ... ``` for clarity. -8. **Important:** Do not wrap any XML output in CDATA tags (i.e. ``). Repo Prompt expects raw XML exactly as shown in the examples. +8. **Important:** Do not wrap any XML output in CDATA tags (i.e. ``). We xpect raw XML exactly as shown in the examples. 9. **IMPORTANT** IF MAKING FILE CHANGES, YOU MUST USE THE AVAILABLE XML FORMATTING CAPABILITIES PROVIDED ABOVE - IT IS THE ONLY WAY FOR YOUR CHANGES TO BE APPLIED. 10. The final output must apply cleanly with no leftover syntax errors. \ No newline at end of file