Go Common Practice

The Go-specific base layer for the golang-* skill family.

Scope

This skill provides engineering guidance for any agent. Follow the user's task, repository conventions, and host permissions; no role hierarchy or orchestration framework is assumed.

Use this skill only to improve the quality and verification of already-authorized Go work.

Inner verification loop

After each coherent implementation change, run the smallest relevant check for changed packages or affected behavior. For example, adapt go test ./path/to/package, go build ./path/to/package, or a configured linter to the actual repository. Broaden to ./..., go vet, race detection, vulnerability scans, fuzzing, or benchmarks when changed behavior, repository policy, or credible material risk makes that coverage necessary.

An unrelated existing warning or optional hardening idea is not a mandate to expand the change. Record what was checked and the limits of those results; do not claim full-suite validation from a focused check.

Do not use automatic fix flags as a substitute for understanding changes.

When conclusions rely on test/build/lint/security/runtime results, record the commands, scope, and observed outcomes in the task summary or the project's verification record. Distinguish unrun checks and limitations from passing results.