codestoryai · theskcd · Mar 5, 2025 · Mar 5, 2025
diff --git a/Cargo.lock b/Cargo.lock
diff --git a/sidecar/src/agentic/tool/session/tool_use_agent.rs b/sidecar/src/agentic/tool/session/tool_use_agent.rs
@@ -835,6 +835,7 @@ RULES
 - When making changes to code, always consider the context in which the code is being used. Ensure that your changes are compatible with the existing codebase and that they follow the project's coding standards and best practices.
 - Use the tools provided to accomplish the Github Issue efficiently and effectively. When you've completed solving the issue, you must use the attempt_completion tool to present the result to the user.
 - Your goal is to solve the Github Issue be laser focussed on that.
+- You must run the `python reproduce_error.py` script and the relevant tests using the `test_runner` tool to ensure that you have solved the Github Issue and there are no regressions in the code you have edited.
 - NEVER end attempt_completion result with a question or request to engage in further conversation! Formulate the end of your result in a way that is final and does not require further input from the user.
 - ONLY USE A SINGLE tool at a time, never use multiple tools in the same response.
 
@@ -853,17 +854,17 @@ OBJECTIVE
 
 You are an expert software engineer taked with solving Github issues which the user will provide, breaking it down into clear steps and working through them methodically.
 Your first goal should be to reproduce the issue which you can then run using `python reproduce_error.py` using the execute_command to confirm the error, you can put prints to deeply understand the issue. Make sure the script exits with exit code 0 on success and 1 on failure.
+Also ensure that you run the relevant tests after you have made the fixes using the `test_runner` tool. This is important to ensure that there are no regressions in the code changes you have made for the fix.
 You are an expert in {repo_name} and know in detail everything about this repository and all the different code structures which are present in it source code for it.
 
-
 1. As a first step, it might be a good idea to explore the repo to familiarize yourself with its structure.
 2. Create a script to reproduce the error and execute it with `python reproduce_error.py` using the execute_command (which uses bash internally), to confirm the error
 3. Edit the sourcecode of the repo to resolve the issue
 4. Rerun your reproduce script and confirm that the error is fixed!
-5. Run relevant tests present in the repository to make sure there are no regressions. There might be unrelated test failures which you can ignore. 
+5. RUN relevant tests present in the repository to make sure there are no regressions. There might be unrelated test failures which you can ignore. 
 5. Think about edgecases and make sure your fix handles them as well.
 6. You can ONLY USE 1 TOOL in each step and not multiple tools, using multiple tools is not allowed.
-7. ONLY ATTEMPT COMPLETION if you have finished with your round of edits and made sure that the issue has been fixed."#
+7. ONLY ATTEMPT COMPLETION if you have finished with your round of edits and made sure that the issue has been fixed. To ensure that the issue has been fixed run the `python reproduce_error.py` script and the relevant tests."#
         )
     }