go-quality-cli-agent

Go concurrency patterns, context propagation, goroutine lifecycle, channel ownership, sync primitives, goroutine leak prevention, and race detector usage. Use when writing or reviewing concurrent Go code.

Go error handling patterns: %w wrapping, errors.Is/As, sentinel errors, custom error types, panic prohibition rules, and error API design. Use when writing or reviewing error handling code.

Go Standard Project Layout: /cmd, /internal, /pkg conventions, import organization, goimports, circular dependency prevention, and module boundaries. Use when scaffolding or reviewing Go project structure.

Go security scanning: govulncheck, gosec, dependency vulnerabilities, SQL injection prevention, hardcoded secrets, and unsafe usage. Use when answering security questions or scanning Go projects.

Go style and formatting guidelines: gofmt, goimports, naming conventions, comment standards, Effective Go idioms, and golangci-lint configuration. Use when reviewing or formatting Go code.

Go testing standards: table-driven tests, testify, mockgen, coverage measurement, race-safe tests, benchmark correctness, and test isolation patterns. Use when writing, reviewing, or running Go tests.

Go performance profiling workflows: CPU profiling, memory profiling, benchmarking, goroutine/block/mutex profiling, execution tracing, and pprof analysis. Use when asked to profile performance, analyze memory usage, find CPU hotspots, run/compare benchmarks, or investigate slow Go code.

Go package dependency analysis and call graph visualization using goda, go-callvis, go mod graph, and go list. Use when asked to visualize architecture, understand package relationships, find circular dependencies, or map call flows in a Go project. Equivalent to "und export -dependencies" from SciTools Understand.

Go code quality and compliance analysis using golangci-lint, staticcheck, go vet, and revive. Use when asked to check code quality, find linting violations, audit Go code for correctness, or when the user asks "what's wrong with this code?" for a Go project.

Go code metrics: cyclomatic complexity (gocyclo), cognitive complexity (gocognit), lines of code statistics (gocloc), and package-level inventory via go list. Use when asked about code complexity, maintainability scores, code size statistics, or to find the most complex/largest functions. Equivalent to "und metrics" from SciTools Understand.