Update Claude workflow and documentation for commit message guidelines

Author: mxpv

.github/workflows/claude-code-review.yml

@@ -19,9 +19,9 @@ jobs:
       (github.event_name == 'issues' && (contains(github.event.issue.body, '@claude') || contains(github.event.issue.title, '@claude')))
     runs-on: ubuntu-latest
     permissions:
-      contents: read
-      pull-requests: read
-      issues: read
+      contents: write
+      pull-requests: write
+      issues: write
       id-token: write
       actions: read # Required for Claude to read CI results on PRs
     steps:
@@ -39,26 +39,18 @@ jobs:
           # This is an optional setting that allows Claude to read CI results on PRs
           additional_permissions: |
             actions: read
-          
-          # Optional: Specify model (defaults to Claude Sonnet 4, uncomment for Claude Opus 4)
-          # model: "claude-opus-4-20250514"
-          
-          # Optional: Customize the trigger phrase (default: @claude)
-          # trigger_phrase: "/claude"
-          
-          # Optional: Trigger when specific user is assigned to an issue
-          # assignee_trigger: "claude-bot"
-          
-          # Optional: Allow Claude to run specific commands
-          # allowed_tools: "Bash(npm install),Bash(npm run build),Bash(npm run test:*),Bash(npm run lint:*)"
-          
+
+          model: "claude-opus-4-20250514"
+
+          allowed_tools: "Bash(go:*),Bash(golangci-lint:*),Bash(make:*),View,GlobTool,GrepTool,BatchTool,mcp__github"
+
           # Optional: Add custom instructions for Claude to customize its behavior for your project
-          # custom_instructions: |
-          #   Follow our coding standards
-          #   Ensure all new code has tests
-          #   Use TypeScript for new files
-          
-          # Optional: Custom environment variables for Claude
-          # claude_env: |
-          #   NODE_ENV: test
+          custom_instructions: |
+            Follow our coding standards
+            Ensure tests and lints pass before making commits or PRs
+            Run 'make test' to verify all tests pass
+            Use Go conventions and best practices
+            When reviewing code: provide brief summary of changes,
+            list concerns as bullets (keep short and understandable),
+            end with approval status using red/green icons for visibility.
 

.github/workflows/claude.yml

@@ -88,6 +88,8 @@ The application uses TOML configuration files. See `config.toml.example` for all
 ### Git Workflow
 - Write short, expressive commit messages that clearly describe the change
 - Do not include automated signatures or generation notices in commit messages
+- Don't add "Generated with Claude Code" to commit messages
+- Don't add "Co-Authored-By: Claude [email protected]" to commit messages
 - Keep commits focused and atomic - one logical change per commit
 - Ensure the build passes before pushing commits