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
Copy file name to clipboardExpand all lines: api/src/agent/agent.prompts.ts
-44Lines changed: 0 additions & 44 deletions
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,6 @@ import {
3
3
typePlanPromptContext,
4
4
typePrBodyPromptContext,
5
5
typeRevisePromptContext,
6
-
typeTestPromptContext,
7
6
}from'./agent.model.js';
8
7
9
8
constPLAN_OUTPUT_CONTRACT=`Your response MUST be the complete, detailed implementation plan — not a statement of intent and not a preamble. Use your tools to fully explore the codebase first, then output the full plan in a single response.
@@ -117,46 +116,3 @@ export function buildPrBodyPrompt(ctx: PrBodyPromptContext): string {
117
116
`Output ONLY the PR body as GitHub-flavored Markdown. No preamble, no explanation — just the content.`,
118
117
].join('\n\n');
119
118
}
120
-
121
-
constTEST_OUTPUT_CONTRACT=`Output your verdict as the FIRST thing in your response — a \`\`\`json block before any other text:
122
-
\`\`\`json
123
-
{
124
-
"passed": true | false,
125
-
"summary": "<one-paragraph summary of what ran and the overall outcome>",
126
-
"failures": [
127
-
{ "name": "<test name, command, or category that failed>", "detail": "<what went wrong and any relevant output>" }
128
-
]
129
-
}
130
-
\`\`\`
131
-
Set "passed" to true only if ALL tests pass AND the application starts and runs correctly. Use an empty array for "failures" when passing. You may include detailed output after the JSON block.`;
`You are Hermes, an autonomous engineer working in a clone of \`${ctx.repoFullName}\`. Your task is to verify the implementation for: **${ctx.issueTitle}**.`,
136
-
`--- APPROVED PLAN ---\n${ctx.plan}\n--- END PLAN ---`,
137
-
`Instructions:
138
-
1. Discover the test suite by inspecting the project structure (look for \`package.json\` test scripts, \`pytest.ini\`, \`jest.config.*\`, \`vitest.config.*\`, \`go.mod\`, \`Makefile\`, etc.).
139
-
2. Run the tests and capture the full output.
140
-
3. **Try to run the application itself** — start the dev server, CLI, or process and verify it launches without errors. For web/browser applications, open the running app in the browser and exercise the key user flows from the acceptance criteria. For CLI tools, invoke the main commands and check the output.
141
-
4. Do NOT modify any source files — if tests fail or the application errors, document what went wrong. Fixes are handled in a separate step.`,
142
-
];
143
-
144
-
if(ctx.hasBrowser){
145
-
parts.push(
146
-
`A Camofox browser is available. Use it to open the running application and manually verify the acceptance criteria — click through real user flows, not just check that the page loads.`,
147
-
);
148
-
}
149
-
150
-
if(ctx.priorOutput){
151
-
parts.push(
152
-
`The previous test run ended with this output — use it as your starting point:\n\`\`\`\n${ctx.priorOutput.slice(0,4000)}\n\`\`\``,
153
-
);
154
-
}
155
-
156
-
parts.push(
157
-
`Use \`.olympian/\` as a scratch directory for any temporary files (diffs, logs, etc.) — it is excluded from commits automatically. Do not run git yourself.`,
constTEST_OUTPUT_CONTRACT=`Output your verdict as the FIRST thing in your response — a \`\`\`json block before any other text:
4
+
\`\`\`json
5
+
{
6
+
"passed": true | false,
7
+
"summary": "<one-paragraph summary of what ran and the overall outcome>",
8
+
"failures": [
9
+
{ "name": "<test name, command, or category that failed>", "detail": "<what went wrong and any relevant output>" }
10
+
]
11
+
}
12
+
\`\`\`
13
+
Set "passed" to true only if ALL tests pass AND the application starts and runs correctly. Use an empty array for "failures" when passing. You may include detailed output after the JSON block.`;
`You are Hermes, an autonomous engineer working in a clone of \`${ctx.repoFullName}\`. Your task is to verify the implementation for: **${ctx.issueTitle}**.`,
18
+
`--- APPROVED PLAN ---\n${ctx.plan}\n--- END PLAN ---`,
19
+
`Instructions:
20
+
1. Discover the test suite by inspecting the project structure (look for \`package.json\` test scripts, \`pytest.ini\`, \`jest.config.*\`, \`vitest.config.*\`, \`go.mod\`, \`Makefile\`, etc.).
21
+
2. Run the tests and capture the full output.
22
+
3. **Try to run the application itself** — start the dev server, CLI, or process and verify it launches without errors. For web/browser applications, open the running app in the browser and exercise the key user flows from the acceptance criteria. For CLI tools, invoke the main commands and check the output.
23
+
4. Do NOT modify any source files — if tests fail or the application errors, document what went wrong. Fixes are handled in a separate step.`,
24
+
];
25
+
26
+
if(ctx.hasBrowser){
27
+
parts.push(
28
+
`A Camofox browser is available. Use it to open the running application and manually verify the acceptance criteria — click through real user flows, not just check that the page loads.`,
29
+
);
30
+
}
31
+
32
+
if(ctx.priorOutput){
33
+
parts.push(
34
+
`The previous test run ended with this output — use it as your starting point:\n\`\`\`\n${ctx.priorOutput.slice(0,4000)}\n\`\`\``,
35
+
);
36
+
}
37
+
38
+
parts.push(
39
+
`Use \`.olympian/\` as a scratch directory for any temporary files (diffs, logs, etc.) — it is excluded from commits automatically. Do not run git yourself.`,
0 commit comments