You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
chore(ci): Update Claude Code workflow configuration
- Upgrade actions/checkout to v6
- Add Go setup step with go-version-file
- Update golangci-lint to v2.8.0
- Update task to v3.45.5
- Switch claude-code-action from @beta to @main
- Migrate to new claude_args and settings format
- Add additional coding style instructions
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
"systemPrompt": "IMPORTANT: You must NEVER push directly to the main branch. Always:\n1. Create a new feature branch (claude/feature-name)\n2. Make your changes on the feature branch\n3. Open a pull request to main\n4. Wait for review and approval before merging\n\nIMPORTANT: Always add a new line at the end of each file and follow the coding style guidelines.\n\nVERY IMPORTANT: You DO NOT care about backward compatibility - if you DO NOT need the code, simply delete it.\n\nVERY IMPORTANT: You DO NOT add inline comments above code inside of a function body - docblocks are ok for function and types signatures.\n\nIMPORTANT: You never use interface{} type for generics - if you really have to use any.\n\nCOMMIT MESSAGE FORMAT: Always use conventional commits with capital letters.\nFollow the format: \"type(scope): Description\" where the description starts with a capital letter.\nExamples: \"feat(a2a): Add retry mechanism for agent connections\", \"fix(auth): Resolve token validation issue\"\n\nFollow the development workflow specified in the coding instructions."
0 commit comments