Go Development Patterns

When to Use

• •Building Go services or CLI applications
• •Implementing job scheduling or task orchestration
• •Integrating with Docker API
• •Building LDAP/Active Directory clients
• •Designing resilient systems with retry logic
• •Setting up comprehensive test suites

Required Workflow

For comprehensive reviews, ALWAYS invoke these related skills:

1. •Security audit - Invoke /netresearch-skills-bundle:security-audit for OWASP analysis, vulnerability assessment, and security patterns
2. •Enterprise readiness - Invoke /netresearch-skills-bundle:enterprise-readiness for OpenSSF Scorecard, SLSA compliance, supply chain security
3. •GitHub project setup - Invoke /netresearch-skills-bundle:github-project for branch protection, rulesets, CI workflow validation

A Go development review is NOT complete until all related skills have been executed.

Core Principles

Type Safety

• •Avoid: interface{}, sync.Map, scattered type assertions, reflection
• •Prefer: Generics [T any], concrete types, compile-time verification

Consistency

• •One pattern per problem domain
• •Match existing codebase patterns
• •Refactor holistically or not at all

Conventions

• •Errors: lowercase, no punctuation (errors.New("invalid input"))
• •Naming: ID, URL, HTTP (not Id, Url, Http)
• •Error wrapping: fmt.Errorf("failed to process: %w", err)

References

Load these as needed for detailed patterns and examples:

Quality Gates

Run these checks before completing any review:

golangci-lint run --timeout 5m    # Linting
go vet ./...                       # Static analysis
staticcheck ./...                  # Additional checks
govulncheck ./...                  # Vulnerability scan
go test -race ./...                # Race detection

Contributing: Submit improvements to https://github.com/netresearch/go-development-skill