ShockVPN/shockbot
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Tweak prompts, switch to opus

Browse Source
This commit is contained in:
Colin McDonnell
2025-12-22 17:40:40 -08:00
parent 7103f5f991
commit dcb672b5be
4 changed files with 7 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
agents/claude.ts
+2
View File
@@ -53,9 +53,11 @@ export const claude = agent({
// This ensures secrets are only available to Claude Code subprocess, not user code
const queryInstance = query({
prompt,
options: {
...sandboxOptions,
mcpServers,
model: "claude-opus-4-5",
pathToClaudeCodeExecutable: cliPath,
env: createAgentEnv({ ANTHROPIC_API_KEY: apiKey }),
},
entry
+3 -4
View File
@@ -92638,9 +92638,7 @@ ${disableProgressComment ? "" : `
- Is the approach sound? If not, focus on the approach first. Don't waste time on implementation details if the approach is wrong.
- What bugs, edge cases, or security issues exist?
4. **DRAFT** - For each inline comment, find the line in the diff. Each code line shows: \`OLD | NEW | TYPE | code\`
- For added lines (\`+\`) or context lines, use the NEW line number (second column)
- For removed lines (\`-\`), use the OLD line number (first column) with \`side: "LEFT"\`
4. **DRAFT** - For each inline comment, find the line in the diff. Each code line shows: \`OLD | NEW | TYPE | CODE\`. Use the NEW line number (second column).
5. **SELF-CRITIQUE** - Before submitting, review your draft:
- DO NOT NITPICK. Do not comment on minor formatting changes, changes to playground/scratch files, lack of docs/docsstrings, or small changes that seem irrelevant. Assume these things are intentional by the PR author.
@@ -93341,6 +93339,7 @@ var claude = agent({
options: {
...sandboxOptions,
mcpServers,
model: "claude-opus-4-5",
pathToClaudeCodeExecutable: cliPath,
env: createAgentEnv({ ANTHROPIC_API_KEY: apiKey })
}
@@ -124536,7 +124535,7 @@ var CreatePullRequestReview = type({
comments: type({
path: type.string.describe("The file path to comment on (relative to repo root)"),
line: type.number.describe(
"Line number from the diff. Each code line shows 'OLD | NEW | TYPE | code'. Use NEW (second column) for added/context lines, OLD (first column) for removed lines."
"Line number from the diff. Each code line shows 'OLD | NEW | TYPE | CODE'. Use the NEW column (second column)."
),
side: type.enumerated("LEFT", "RIGHT").describe(
"Side of the diff: LEFT (old code, lines starting with -) or RIGHT (new code, lines starting with + or unchanged). Defaults to RIGHT."
mcp/review.ts
+1 -1
View File
@@ -20,7 +20,7 @@ export const CreatePullRequestReview = type({
comments: type({
path: type.string.describe("The file path to comment on (relative to repo root)"),
line: type.number.describe(
"Line number from the diff. Each code line shows 'OLD | NEW | TYPE | code'. Use NEW (second column) for added/context lines, OLD (first column) for removed lines."
"Line number from the diff. Each code line shows 'OLD | NEW | TYPE | CODE'. Use the NEW column (second column)."
),
side: type
.enumerated("LEFT", "RIGHT")
modes.ts
+1 -3
View File
@@ -110,9 +110,7 @@ ${
- Is the approach sound? If not, focus on the approach first. Don't waste time on implementation details if the approach is wrong.
- What bugs, edge cases, or security issues exist?
4. **DRAFT** - For each inline comment, find the line in the diff. Each code line shows: \`OLD | NEW | TYPE | code\`
- For added lines (\`+\`) or context lines, use the NEW line number (second column)
- For removed lines (\`-\`), use the OLD line number (first column) with \`side: "LEFT"\`
4. **DRAFT** - For each inline comment, find the line in the diff. Each code line shows: \`OLD | NEW | TYPE | CODE\`. Use the NEW line number (second column).
5. **SELF-CRITIQUE** - Before submitting, review your draft:
- DO NOT NITPICK. Do not comment on minor formatting changes, changes to playground/scratch files, lack of docs/docsstrings, or small changes that seem irrelevant. Assume these things are intentional by the PR author.