Go Linting

What it does

This skill enables AI agents to identify potential errors and style issues in Go code using golangci-lint. It leverages a configurable set of linters to enforce consistent coding standards, catch common mistakes, and improve overall code quality. The tool prioritizes consistency over strict adherence to any single linter's ruleset.

When to use it

• When ensuring code adheres to project style guidelines.
• Before committing code changes to a repository.
• As part of an automated CI/CD pipeline for continuous code analysis.
• To identify and address potential security vulnerabilities in Go applications (with the gosec linter).
• When refactoring existing Go codebases to improve maintainability.

Key capabilities

• Runs a suite of linters including errcheck, goimports, revive, govet, and staticcheck.
• Supports configuration via .golangci.yml files, allowing customization of enabled linters and their settings.
• Provides guidance on resolving linting errors category by category (formatting, vet, then style).
• Includes example configurations for common scenarios.
• Offers recommendations for additional linters to enhance code quality and security.

Example prompts

• "Run the Go linter on this file: main.go."
• "Analyze the entire project directory for linting issues."
• "Check if these changes introduce any new linting errors."

Tips & gotchas

• A .golangci.yml configuration file is required in the project root. The skill provides an example to use as a baseline.
• When suppressing linting warnings using //nolint, always include a justification for why the warning is being ignored.
• For optimal results, run linters consistently across the entire codebase.