go-build-resolver_skill

Overview

This skill is a Go build, vet, and compilation error resolution specialist that applies minimal, surgical changes to make builds succeed. It diagnoses compilation errors, resolves go vet and linter warnings, and handles module and type mismatches while preserving code intent.

How this skill works

I run standard diagnostic commands (go build, go vet, staticcheck/golangci-lint if available, and go mod tidy/verify) to capture errors and warnings. For each failure I identify the file and line, determine the root cause (undefined identifier, type mismatch, interface mismatch, import cycle, missing package, etc.), apply the smallest change that fixes the issue, and re-run the checks until the build is clean or a stop condition is met.

When to use it

• When go build ./... fails with compilation errors
• When go vet or linters surface warnings that block CI
• When module dependency errors or checksum mismatches occur
• When type or interface mismatches prevent compilation
• When import cycles or missing package errors appear during build

Best practices

• Make minimal, surgical changes—avoid broad refactors
• Always read the full error and go to the indicated file/line
• Run go mod tidy after adding/removing imports
• Prefer fixing the root cause over suppressing errors (no //nolint by default)
• Document non-obvious fixes with a short inline comment

Example use cases

• Add a missing import to resolve an undefined identifier error
• Adjust types or add conversions to fix cannot use X as type Y
• Implement a missing method or change receiver type to satisfy an interface
• Break an import cycle by extracting shared types into a new package
• Resolve module version conflicts with go get package@version and go mod tidy