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: .agents/templates/git-committer-user-prompt.md
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,7 @@
1
1
Please follow the below steps to create a good commit message:
2
2
3
3
1.**Run two run_terminal_command tool calls:**
4
+
4
5
- Run \`git diff\` to review both staged and unstaged modifications.
5
6
- Run \`git log\` to check recent commit messages, ensuring consistency with this repository’s style.
6
7
@@ -9,8 +10,9 @@ Please follow the below steps to create a good commit message:
9
10
3.**Select relevant files to include in the commit:**
10
11
Use the git and file context to decide which files are pertinent to the changes. Stage any new untracked files that are relevant, but avoid committing previously modified files (from the beginning of the conversation) unless they directly relate to this commit.
11
12
12
-
3.**Analyze the staged changes and compose a commit message:**
13
+
4.**Analyze the staged changes and compose a commit message:**
13
14
Enclose your analysis in <commit_analysis> tags. Within these tags, you should:
15
+
14
16
- Note which files have been altered or added.
15
17
- Categorize the nature of the changes (e.g., new feature, fix, refactor, documentation, etc.).
16
18
- Consider the purpose or motivation behind the alterations.
@@ -22,7 +24,7 @@ Please follow the below steps to create a good commit message:
22
24
- Ensure the message provides clarity—avoid generic or vague terms like “Update” or “Fix” without context.
23
25
- Revisit your draft to confirm it truly reflects the changes and their intention.
24
26
25
-
4.**Create the commit, ending with this specific footer:**
27
+
5.**Create the commit, ending with this specific footer:**
26
28
\`\`\`
27
29
Generated with Codebuff 🤖
28
30
Co-Authored-By: Codebuff <noreply@codebuff.com>
@@ -48,7 +50,7 @@ Please follow the below steps to create a good commit message:
48
50
- Make sure your commit message is concise yet descriptive, focusing on the intention behind the changes rather than merely describing them.
49
51
50
52
5.**Wrapping up**
51
-
Finally, after creating the commit, you should use the update_report tool with a concise summary of what you committed and whether it was successful.
52
-
Use end_turn to end your turn immediately after using the update_report tool.
53
+
Finally, after creating the commit, you should use the set_output tool with a structured summary of what you committed and whether it was successful. The output should include fields like `success`, `message`, and `commitHash` if available.
54
+
Use end_turn to end your turn immediately after using the set_output tool.
53
55
54
-
There's no need to write anything else outside these tool calls.
56
+
There's no need to write anything else outside these tool calls.
Copy file name to clipboardExpand all lines: .agents/templates/git-committer.ts
+4-6Lines changed: 4 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -3,9 +3,7 @@ import { DynamicAgentConfig } from '@codebuff/common/types/dynamic-agent-templat
3
3
exportdefault{
4
4
id: 'CodebuffAI/git-committer',
5
5
version: '0.0.1',
6
-
model: 'google/gemini-2.5-pro',
7
-
override: false,
8
-
// implementation: 'llm',
6
+
model: 'anthropic/claude-sonnet-4',
9
7
name: 'Git Committer',
10
8
purpose:
11
9
'A git committer agent specialized to commit current changes with an appropriate commit message.',
@@ -16,11 +14,11 @@ export default {
16
14
},
17
15
},
18
16
includeMessageHistory: false,
19
-
outputMode: 'report',
17
+
outputMode: 'json',
20
18
toolNames: [
21
19
'read_files',
22
20
'run_terminal_command',
23
-
'update_report',
21
+
'set_output',
24
22
'think_deeply',
25
23
'end_turn',
26
24
],
@@ -30,5 +28,5 @@ export default {
30
28
path: './git-committer-user-prompt.md',
31
29
},
32
30
agentStepPrompt:
33
-
'Make sure to end your response by using update_report to update the report with a concise summary of what you committed and whether it was successful. Finally, use end_turn to end your turn.',
31
+
'Make sure to end your response by using set_output to output a structured summary of what you committed and whether it was successful. Finally, use end_turn to end your turn.',
0 commit comments