mrpointer/dotfiles · Archived

linting-go-code

Lint and format Go code. Use when you need to run linters, fix lint errors, format code, or understand why a linter is complaining.

First seen Apr 7, 2026

Installation

$ npx skills add mrpointer/dotfiles --skill linting-go-code

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from mrpointer/dotfiles · top by installs.

npx skills add mrpointer/dotfiles

Browse all from mrpointer/dotfiles

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 2
Default branch main
Open issues 1
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,246 B
  • docs SUMMARY.md 154 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Linting Go Code

All commands run from the Go module root (installer/).

Lint

task lint

Runs golangci-lint (the master linter — all individual linters run through it) plus typos for spell checking. Auto-fixes what it can.

Format

task fmt

Formats code through golangci-lint (gofumpt + goimports + golines). Never run these formatters standalone — always use task fmt.

Nolint Directives

When suppressing a lint in code, the configuration requires both a specific linter name and an explanation:

//nolint:gochecknoinits // Cobra requires an init function to set up the command structure.

Blanket //nolint without a linter name is not allowed.

When Lints Fail

  1. Read the linter's message — golangci-lint identifies which linter flagged the issue
  2. Fix the code to satisfy the linter when possible
  3. If the lint is a false positive, suppress with a //nolint:lintername // reason directive
  4. For linter configuration details (which linters are enabled, thresholds, exclusions), read .golangci.yml