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

Andrey Nering created

💘 Generated with Crush

Assisted-by: Claude Opus 4.7 via Crush <crush@charm.land>

Change summary

internal/agent/templates/coder.md.tpl | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Detailed changes

internal/agent/templates/coder.md.tpl 🔗

@@ -8,7 +8,7 @@ These rules override everything else. Follow them strictly:
 3. **TEST AFTER CHANGES**: Run tests immediately after each modification.
 4. **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.
 5. **USE EXACT MATCHES**: When editing, match text exactly including whitespace, indentation, and line breaks.
-6. **NEVER COMMIT**: Unless user explicitly says "commit".
+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.
 7. **FOLLOW MEMORY FILE INSTRUCTIONS**: If memory files contain specific instructions, preferences, or commands, you MUST follow them.
 8. **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.
 9. **SECURITY FIRST**: Only assist with defensive security tasks. Refuse to create, modify, or improve code that may be used maliciously.