You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -126,13 +126,12 @@ Try to select an implementation that fulfills all the requirements in the user's
126
126
127
127
## Response Format
128
128
129
-
${
130
-
isSonnet||isOpus
131
-
? `Use <think> tags to write out your thoughts about the implementations as needed to pick the best implementation. IMPORTANT: You should think really really hard to make sure you pick the absolute best implementation! Also analyze the non-chosen implementations for any valuable techniques or approaches that could improve the selected one.
129
+
${isSonnet||isOpus
130
+
? `Use <think> tags to write out your thoughts about the implementations as needed to pick the best implementation. IMPORTANT: You should think really really hard to make sure you pick the absolute best implementation! Also analyze the non-chosen implementations for any valuable techniques or approaches that could improve the selected one.
132
131
133
132
Then, do not write any other explanations AT ALL. You should directly output a single tool call to set_output with the selected implementationId, short reason, and suggestedImprovements array.`
134
-
: `Output a single tool call to set_output with the selected implementationId, reason, and suggestedImprovements. Do not write anything else.`
135
-
}`,
133
+
: `Output a single tool call to set_output with the selected implementationId, reason, and suggestedImprovements. Do not write anything else.`
@@ -67,10 +67,9 @@ OR for new files or major rewrites:
67
67
"content": "Complete file content or edit snippet"
68
68
}
69
69
</codebuff_tool_call>
70
-
${
71
-
isGpt5||isGemini
72
-
? ``
73
-
: `
70
+
${isGpt5||isGemini
71
+
? ``
72
+
: `
74
73
IMPORTANT: Before you start writing your implementation, you should use <think> tags to think about the best way to implement the changes. You should think really really hard to make sure you implement the changes in the best way possible. Take as much time as you to think through all the cases to produce the best changes.
75
74
76
75
You can also use <think> tags interspersed between tool calls to think about the best way to implement the changes.
@@ -98,7 +97,7 @@ You can also use <think> tags interspersed between tool calls to think about the
98
97
</codebuff_tool_call>
99
98
100
99
</example>`
101
-
}
100
+
}
102
101
103
102
After the edit tool calls, you can optionally mention any follow-up steps to take, like deleting a file, or a specific way to validate the changes. There's no need to use the set_output tool as your entire response will be included in the output.
'Edits code by spawning multiple implementor agents with different strategy prompts, selects the best implementation, and applies the changes. It also returns further suggested improvements which you should take seriously and act on. Pass as input an array of short prompts specifying different implementation approaches or strategies. Make sure to read any files intended to be edited before spawning this agent.',
Copy file name to clipboardExpand all lines: agents/reviewer/multi-prompt/code-reviewer-multi-prompt.ts
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ export function createCodeReviewerMultiPrompt(): Omit<
14
14
>{
15
15
return{
16
16
publisher,
17
-
model: 'anthropic/claude-opus-4.5',
17
+
model: 'anthropic/claude-opus-4.6',
18
18
displayName: 'Multi-Prompt Code Reviewer',
19
19
spawnerPrompt:
20
20
'Reviews code by spawning multiple code-reviewer agents with different focus prompts, then combines all review outputs into a comprehensive review. Make sure to read relevant files before spawning this agent. Pass an input array of short prompts specifying several different review focuses or perspectives.',
0 commit comments