golang-development

Design or audit Go application architecture, package boundaries, dependency direction, interfaces, adapters, repositories, services, HTTP handlers, concurrency boundaries, and maintainable design patterns. Use for Golang service design, refactors, domain layering, dependency injection, ports/adapters, repository patterns, functional options, API design, concurrency architecture, or reviewing existing Go architecture for coupling and maintainability risks.

Build, package, release, containerize, deploy, or audit Go applications and CLIs. Use for Golang build flags, module release checks, cross-compilation, Dockerfiles, CI/CD, version metadata, graceful shutdown, runtime configuration, security updates, production deployment plans, or reviewing existing Go release/deployment readiness.

Audit existing Go and Golang codebases, pull requests, diffs, packages, services, CLIs, tests, build pipelines, and repository layouts against idiomatic Go development guidance. Use when reviewing, auditing, assessing, evaluating, inspecting, checking best-practice compliance, finding violations, identifying risks, or producing findings for already-built Go code.

Route Go and Golang development work into the right build or audit workflow. Use for broad Go tasks such as building features, implementing changes, refactoring, planning, reviewing, auditing, assessing an existing codebase, checking against Go best practices, or deciding which Golang Development skills apply.

Implement or audit idiomatic Go code using effective naming, errors, context, interfaces, generics, nil handling, slices/maps, documentation comments, and standard library conventions. Use when writing, refactoring, cleaning, or reviewing Golang code; reducing nesting; improving API ergonomics; checking idiomatic implementation style; or finding non-idiomatic Go in existing code.

Plan or audit idiomatic Go modules, repository layout, package boundaries, command structure, migration strategy, and implementation plans. Use when working on Go or Golang projects before adding packages, moving code, choosing cmd/internal/pkg layout, splitting modules, introducing workspaces, writing a multi-step implementation plan, or reviewing an existing repo for layout and package-boundary problems.

Verify, improve, or audit Go code quality with gofmt, goimports, go vet, static analysis, golangci-lint, security checks, code review, lint configuration, and completion verification. Use when reviewing Golang changes, fixing linter failures, setting up golangci-lint, deciding quality gates, auditing existing quality practices, or checking whether Go code is ready to ship.

Add, repair, design, or audit Go tests using the standard testing package, table-driven tests, subtests, examples, benchmarks, fuzz tests, race checks, coverage, fakes, and integration-test boundaries. Use when testing Golang code, creating test plans, debugging failing go test output, deciding unit vs integration coverage, reviewing test quality, finding missing coverage, or assessing whether existing tests prove behavior.