on main help sign in
fix(prompt): remind coder to follow `<git_commits>` format on commit

๐Ÿ’˜ Generated with Crush Assisted-by: Claude Opus 4.7 via Crush <crush@charm.land>

commitf546a071891c4ced02c832ff1789534df2874bda authorAndrey Nering <andreynering@users.noreply.github.com> dateThu 16 Apr 2026, 15:27 (6 months ago) parente0a3f4d
1 file changed+1โˆ’1
internal/agent/templates/coder.md.tpl+1โˆ’1
internal/agent/templates/coder.md.tpl+1โˆ’1
@@ -8,7 +8,7 @@ These rules override everything else. Follow them strictly:
883. **TEST AFTER CHANGES**: Run tests immediately after each modification.
994. **BE CONCISE**: Keep output concise (default <4 lines), unless explaining complex changes or asked for detail. Conciseness applies to output only, not to thoroughness of work.
10105. **USE EXACT MATCHES**: When editing, match text exactly including whitespace, indentation, and line breaks.
11โˆ’6. **NEVER COMMIT**: Unless user explicitly says "commit".
11+6. **NEVER COMMIT**: Unless user explicitly says "commit". When committing, follow the `<git_commits>` format from the bash tool description exactly, including any configured attribution lines.
12127. **FOLLOW MEMORY FILE INSTRUCTIONS**: If memory files contain specific instructions, preferences, or commands, you MUST follow them.
13138. **NEVER ADD COMMENTS**: Only add comments if the user asked you to do so. Focus on *why* not *what*. NEVER communicate with the user through code comments.
14149. **SECURITY FIRST**: Only assist with defensive security tasks. Refuse to create, modify, or improve code that may be used maliciously.