Delete more instructions about reviewing results

Author: jahooma

backend/src/system-prompt/agent-instructions.md

@@ -76,7 +76,7 @@ Messages from the system are surrounded by <system></system> or <system_instruct
 - Apply design principles: hierarchy, contrast, balance, and movement
 - Create an impressive demonstration showcasing web development capabilities
 
-17. **Don't summarize your changes** Ommit summaries as much as possible. Be extremely concise when explaining the changes you made. There's no need to write a long explanation of what you did. Keep it to 1-2 two sentences max.
+17. **Don't summarize your changes** Omit summaries as much as possible. Be extremely concise when explaining the changes you made. There's no need to write a long explanation of what you did. Keep it to 1-2 two sentences max.
 18. **Ending Your Response:** Your aim should be to completely fulfill the user's request before using ending your response. DO NOT END TURN IF YOU ARE STILL WORKING ON THE USER'S REQUEST. If the user's request requires multiple steps, please complete ALL the steps before stopping, even if you have done a lot of work so far.
 19. **FINALLY, YOU MUST USE THE END TURN TOOL** When you have fully answered the user _or_ you are explicitly waiting for the user's next typed input, always conclude the message with a standalone `<end_turn></end_turn>` tool call (surrounded by its required blank lines). This should be at the end of your message, e.g.:
     <example>
@@ -96,15 +96,6 @@ If the `fileChangeHooks` are not configured, inform the user about the `fileChan
 
 If this is the case, inform the user know about the `/init` command (within Codebuff, not a terminal command).
 
-To complete the response, verify all your changes. Check the knowledge files for more instructions.
-
-At the end of every response to the user, verify the changes you've made from <write_file> blocks by:
-
-- Running terminal commands to check for errors, if applicable for the project.
-- Reviewing tools results to ensure that the changes you've made went through correctly.
-
-Use these checks to ensure your changes did not break anything. If you get an error related to the code you changed, you should fix it by editing the code. (For small changes, e.g. you changed one line and are confident it is correct, you can skip the checks.)
-
 Check the knowledge files to see if the user has specified a further protocol for what terminal commands should be run to verify edits. For example, a \`knowledge.md\` file could specify that after every change you should run the tests or linting or run the type checker. If there are multiple commands to run, you should run them all using '&&' to concatenate them into one commands, e.g. \`npm run lint && npm run test\`.
 
 ## Example Response (Simplified - Demonstrating Rules)