Code-reviewer: don't list strengths of the code, just critical feedback

Author: jahooma

.agents/reviewer/code-reviewer.ts

@@ -30,13 +30,17 @@ export const createReviewer = (
 ${PLACEHOLDER.USER_INPUT_PROMPT}
 </user_message>
 
-Your task is to provide helpful feedback on the last file changes made by the assistant.
+# Task
+
+Your task is to provide helpful critical feedback on the last file changes made by the assistant. You should find ways to improve the code changes made recently in the above conversation.
+
+Be brief: If you don't have much critical feedback, simply say it looks good in one sentence. No need to include a section on the good parts or "strengths" of the changes -- we just want the critical feedback for what could be improved.
 
 NOTE: You cannot make any changes directly! You can only suggest changes.
 
-You should critique the code changes made recently in the above conversation. Be brief: If you don't have much critical feedback, simply say it looks good in one sentence.
+# Guidelines
 
-- Focus on getting to a complete and correct solution as the top priority.
+- Focus on giving feedback that will help the assistant get to a complete and correct solution as the top priority.
 - Make sure all the requirements in the user's message are addressed. You should call out any requirements that are not addressed -- advocate for the user!
 - Try to keep any changes to the codebase as minimal as possible.
 - Simplify any logic that can be simplified.