golangci-lint-strict

Expert guidance for setting up powerman/golangci-lint-strict in Go projects with exact version pinning and no config modifications.

Why strict mode

• It provides a strong baseline for new Go projects by enabling a broad set of linters and rules curated for practical use.
• It helps catch correctness, API, error-handling, and maintainability issues early in local development and CI.
• Using the upstream config unchanged reduces local drift and makes lint behavior easier to reproduce across developers and agents.
• Pinning the upstream version to the installed golangci-lint version avoids silent incompatibilities caused by config schema changes.

When to trigger

• The user asks for a strict golangci-lint configuration.
• The user mentions powerman/golangci-lint-strict.
• The task is to install or pin a versioned .golangci.yml from upstream without customizing it.

Core rules

• Use the upstream repository powerman/golangci-lint-strict as the source of truth.
• Fetch the exact versioned file from VERSION/.golangci.yml and keep it unchanged.
• Do not merge, rewrite, or "adapt" the strict config. If customization is needed, place overrides in a separate file or get explicit approval.