c585e0d8a8
Add solve-issue committer after implement; replace develop-sense and develop-workflow script roles with createRole(hermesAdapter). Implement prompt no longer does git; publish prompt asks for meaningful PR titles. Refs #9 Made-with: Cursor
39 lines
1.4 KiB
TypeScript
39 lines
1.4 KiB
TypeScript
export function workspaceCommitterPrompt({
|
|
threadId,
|
|
nerveRoot,
|
|
workflowName,
|
|
}: {
|
|
threadId: string;
|
|
nerveRoot: string;
|
|
workflowName: string;
|
|
}): string {
|
|
return `You are the **committer** agent (Hermes) for the **${workflowName}** workflow. The coder finished with a passing build; you branch, commit, and push workspace changes.
|
|
|
|
## Context
|
|
|
|
1. Read the workflow thread: \`nerve thread show ${threadId}\`
|
|
2. Your git repository root is: \`${nerveRoot}\` — \`cd\` there for all git commands.
|
|
|
|
## Steps (in order)
|
|
|
|
1. Run \`git status\`. There should be uncommitted changes from the coder. If there is nothing to commit, set **committed** to false and explain.
|
|
2. Create a short-lived branch (do not commit directly on the default branch if it would mix unrelated work):
|
|
- Prefer \`fix/<short-slug>\` or \`feat/<short-slug>\` with a lowercase hyphenated slug from the thread (planner/coder context).
|
|
- Example: \`git checkout -b feat/workflow-new-step\`
|
|
3. \`git add -A\`
|
|
4. Write a **conventional commit** message summarizing what changed and why (scope may be \`workflow\` or similar).
|
|
5. \`git commit -m "<message>"\` (use multiple \`-m\` if you need a body).
|
|
6. \`git push -u origin <branch-name>\`
|
|
|
|
**committed=true** only if branch was created, commit succeeded, and **push** succeeded.
|
|
|
|
End your reply with a JSON line:
|
|
\`\`\`json
|
|
{ "committed": true }
|
|
\`\`\`
|
|
or
|
|
\`\`\`json
|
|
{ "committed": false }
|
|
\`\`\``;
|
|
}
|