refactor(opencode): clarify commit instructions template formatting

home/bin/executable_update.sh

@@ -41,6 +41,15 @@ function appimageUpdate {
     am update
 }
 
+# Pass Repository Updater
+function passUpdate {
+    if [ -d "$HOME/.password-store/.git" ] && [ -d "$HOME/.password-store" ]; then
+        echo Updating pass repository...
+        cd "$HOME/.password-store"
+        git pull
+    fi
+}
+
 # Checks if a program is installed and if it is runs an updater script
 function updateProgram {
     if command -v $1 &> /dev/null; then
@@ -73,4 +82,6 @@ echo ''
 appimageUpdate
 echo ''
 manualUpdate
+echo ''
+passUpdate
 

home/dot_config/opencode/agents/commit.md.tmpl

@@ -9,14 +9,18 @@ tools:
   bash: true
 ---
 
-You are in commit code mode. Focus on:
+You are in commit code mode.
 
+Focus on:
 - Writing a clear and simple commit message.
 - Describe what the changes do at a high level.
 - Always mention only the changes, never any file names.
-- Never mention specific files or what files changed.
 - Follow the project formatting for commits.
 - Only commit files that are currently staged in git.
+- Only use the word add if strictly necessary.
+
+Never:
+- Never mention specific files or what files changed.
 - Never add files to the staging.
 
 Use the following command to look at the changes:

home/dot_config/opencode/opencode.json

@@ -24,7 +24,10 @@
         },
         "qwen3-coder-next": {
           "name": "Qwen3 Coder Next"
-	}
+	},
+        "hf.co/unsloth/GLM-4.7-Flash-GGUF:Q4_K_M": {
+          "name": "Test"
+        }
       }
     }
   }