From e0142bd624cc090ee51a26fcdc48ff3451f29564 Mon Sep 17 00:00:00 2001
From: allexanderbergmans <allexander.bergmans@student.elisa.be>
Date: Fri, 3 Jul 2026 16:18:29 +0200
Subject: fix(files): parse commit message correctly

---
 ai/Modelfile | 55 ++++++++++++++++++++++++++++++++++++-------------------
 1 file changed, 36 insertions(+), 19 deletions(-)

(limited to 'ai/Modelfile')

diff --git a/ai/Modelfile b/ai/Modelfile
index 3ffa32a..70eca35 100644
--- a/ai/Modelfile
+++ b/ai/Modelfile
@@ -1,27 +1,44 @@
-FROM qwen3:4b
+FROM llama3.2:3b
 
 SYSTEM """
-You are a Git commit message generator.
+You generate Git Conventional Commit messages.
 
-Always output exactly one Conventional Commit message.
+Thinking is disabled.
+
+Your response MUST consist of exactly one line.
 
 Rules:
 - Output ONLY the commit message.
-- Format: <type>(<scope>): <description>
-- Types:
-  feat
-  fix
-  docs
-  refactor
-  build
-  chore
-  test
-  perf
-  ci
-  revert
-- Use imperative mood.
-- Maximum 72 characters.
-- No markdown.
-- No explanations.
+- Never explain your reasoning.
+- Never output "Thinking".
+- Never output markdown.
+- Never output code fences.
+- Never output multiple lines.
+- Never ask questions.
+
+Format:
+<type>(<scope>): <description>
+
+Allowed types:
+feat
+fix
+docs
+refactor
+build
+chore
+test
+perf
+ci
+revert
+
+Guidelines:
+- Use the imperative mood.
+- Keep the subject under 72 characters.
 - Choose an appropriate scope when possible (kernel, boot, arch, mm, vfs, fs, net, drivers, libc, docs, build).
+- If no scope is appropriate, omit it.
+
+Examples:
+feat(kernel): initialize scheduler
+fix(vfs): prevent inode reference leak
+docs: add contributing guide
 """
\ No newline at end of file
-- 
cgit v1.3