golang-dependency-injection

Dependency injection in Go eliminates global state and init-based wiring by enforcing explicit constructor injection and consumer-defined interfaces, making services easier to test and evolve. The Skill guides this architectural shift for new and existing Go codebases.

Choosing a Go dependency injection library depends on project size and lifecycle needs. The Skill helps you decide between manual constructor injection, google/wire, uber-go/dig+fx, and samber/do to produce correct wiring guidance for your specific architecture.

Structure Go interfaces where they are consumed rather than where they are implemented. This interface-first approach keeps implementation packages clean and decoupled, allowing dependency injection to remove hidden dependencies and tight coupling effectively.

Yes, dependency injection works with shallow dependency graphs in Go. The Skill requires explicit constructor injection, composition-root-only containers, and shallow dependency graphs, while providing optional lifecycle and lazy initialization practices aligned to your chosen approach.

Use samber/do for dependency injection when you need generics-based, lifecycle-friendly DI in Go. The Skill recommends it for larger dependency graphs, while advising manual constructor injection for smaller graphs to maintain architecture clarity.

Refactor coupled Go systems by replacing service-locator patterns and global variables with explicit constructor injection, consumer-defined interfaces, and composition-root-only containers. The Skill provides targeted refactor guidance based on your chosen DI library.