golang-lint

Consolidate Go linting practices and golangci-lint configuration for projects.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/tamago0224/kuroshio-mta --skill golang-lint-tamago0224
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: golang-lint
Source: https://github.com/tamago0224/kuroshio-mta/tree/main/.agents/skills/golang-lint
Command: npx skills add https://github.com/tamago0224/kuroshio-mta --skill golang-lint-tamago0224

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Go projects often suffer from inconsistent linting setups, unclear guidance on lint suppression, and difficulties integrating linters into CI. This skill consolidates linting best practices, a robust golangci-lint configuration, and clear workflows to improve code quality and developer confidence.

Core Features & Use Cases

  • Provides a recommended GolangCI-Lint configuration and guidance on enabling key linters (govet, staticcheck, errcheck, gofumpt) and how to interpret lint results.
  • Includes strategies for incremental adoption and suppression hygiene with nolint directives, plus CI integration tips.
  • Use Case: A Go project with legacy and new code can adopt this skill to stabilize lint results and enforce consistent code quality.

Quick Start

Run the recommended golangci-lint configuration against your module and start addressing flagged issues.

Frequently Asked Questions about golang-lint

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure golangci-lint for consistent Go code quality across a project?

To configure golangci-lint for consistent Go code quality, use a versioned .golangci.yml file that defines enabled linters such as govet, staticcheck, errcheck, and gofumpt alongside per-linter settings and formatter rules.

What is the best way to manage nolint directives in Go static analysis?

Managing nolint directives in Go static analysis requires applying suppression hygiene rules to ensure directives are documented and targeted, preventing broad suppression of legitimate lint warnings across legacy and new code.

How do I integrate Go linting into CI workflows without blocking legacy code adoption?

Integrating Go linting into CI workflows without blocking legacy code involves applying incremental adoption strategies, using a versioned .golangci.yml configuration to stabilize lint results and enforce quality on new code first.

Does golangci-lint support incremental adoption for projects with existing legacy Go code?

golangci-lint supports incremental adoption for projects with legacy Go code by allowing targeted .golangci.yml configurations and nolint directives to isolate new code checks from pre-existing baseline issues.

Why does my Go linting setup produce inconsistent results across different development environments?

Inconsistent Go linting results across environments usually stem from lacking a versioned .golangci.yml file, which standardizes per-linter settings, formatters, and suppression policies for all team workflows.