Preview
Open Original
We are currently looking into incorporating more automated tools in our code review process - particularly around Go best practices (the general spirit is the Google style guide). We already have the basics - golangci-lint as well as cursor bugbot - but I’m more interested in code structure issues (proper dependency injection, usage of interfaces, http best practices).I’d love to hear any advice from own experience.