agentleFS
Sign inStart free
jkeddarijkeddari/go-skills/skills/golang-tooling/SKILL.md

golang-tooling

Skill1 starsChanged 4 months agoMITView on GitHub

Golang linting and modernization workflows using gofmt, go vet, static analysis, golangci-lint, compiler diagnostics, and recent standard-library features. Use when configuring linters, interpreting diagnostics, handling nolint directives, upgrading a Go version, removing deprecated patterns, or modernizing existing Go code.

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the module Go version and existing lint configuration.

    line 23
  2. Distinctive:

    Treat the repository configuration as the source of truth.

    line 31
  3. Distinctive:

    Do not modernize code beyond the module's supported Go version.

    line 33
  4. Distinctive:

    Prefer standard-library replacements only when semantics remain equivalent.

    line 35

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Go Tooling

Workflow

  1. Read the module Go version and existing lint configuration.
  2. Reproduce the diagnostic with the narrowest relevant command.
  3. Understand whether the finding represents correctness, compatibility, performance, or style.
  4. Change source code deliberately; do not apply broad automatic fixes without reviewing the diff.
  5. Re-run the focused check, format modified files, then run affected tests.

Rules

  • Treat the repository configuration as the source of truth.
  • Require a reason for every nolint directive and keep its scope minimal.
  • Do not modernize code beyond the module's supported Go version.
  • Separate mechanical modernization from behavioral refactoring.
  • Prefer standard-library replacements only when semantics remain equivalent.

Conditional references

  • Linter selection and commands: linter-reference.md
  • Suppression policy: nolint-directives.md
  • Version-specific language and library changes: modernize-versions.md
  • Modernization tooling: modernize-tooling.md
  • Reusable lint configuration: .golangci.yml

→ See golang-gopls for semantic navigation and safe rename, and golang-refactoring for structural changes.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free