Update

.config/opencode/opencode.json

@@ -6,8 +6,8 @@
       "temperature": 1.0,
       "top_p": 0.95,
       "permission":{
-        "task": {
-          "git": "allow"
+        "skill": {
+          "git-*": "allow"
         }
       }
     },

.config/opencode/skills/git-commit/SKILL.md

@@ -1,24 +1,10 @@
 ---
-description: Generates git commit message from changes, handle git operations
-mode: subagent
-model: opencode-go/deepseek-v4-flash
-hidden: false
-permission:
-  edit: deny
-  bash: allow
-  read: allow
-  glob: allow
-  grep: allow
-  list: allow
+name: git-commit
+description: Generate git commit messages using Conventional Commits specification
+license: MIT
 ---
 
-Your role is to handle commit.
-You must not compile, build or attempt to make changes as everything has already been tested and confirmed as working as intended.
-All changes are already staged. You must generate a commit message using staged changes and the specification below.
-
-# Commit messages
-
-## Specification
+# Specification
 
 The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119.
 
@@ -39,7 +25,7 @@ The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL
 - The units of information that make up Conventional Commits MUST NOT be treated as case-sensitive by implementors, with the exception of BREAKING CHANGE which MUST be uppercase.
 - BREAKING-CHANGE MUST be synonymous with BREAKING CHANGE, when used as a token in a footer.
 
-## Examples
+# Examples
 
 Commit message with description and breaking change footer
 ```