From f546a071891c4ced02c832ff1789534df2874bda Mon Sep 17 00:00:00 2001 From: Andrey Nering Date: Thu, 16 Apr 2026 15:27:49 -0300 Subject: [PATCH] fix(prompt): remind coder to follow `` format on commit MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 💘 Generated with Crush Assisted-by: Claude Opus 4.7 via Crush --- internal/agent/templates/coder.md.tpl | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/internal/agent/templates/coder.md.tpl b/internal/agent/templates/coder.md.tpl index f9cb2c7da27f220adf88c7115fac8ed86f05d002..c5f28f5590678360a7185e6f9f348382ffde4eb4 100644 --- a/internal/agent/templates/coder.md.tpl +++ b/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 `` 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.