Automate Go dependency injection wiring with uber-go/dig containers.
npx skills add https://github.com/dashkan/pivox --skill golang-uber-dig
Please help me install this Agent Skill. Skill: golang-uber-dig Source: https://github.com/dashkan/pivox/tree/main/.agents/skills/golang-uber-dig Command: npx skills add https://github.com/dashkan/pivox --skill golang-uber-dig
It eliminates brittle, manual construction of complex Go object graphs by letting you declaratively wire dependencies and have dig resolve them safely at composition time.
Provide so each dependency is built once per container and reused where needed.dig.In/dig.Out to manage many dependencies, including named values, value groups, and optional dependencies.dig.Name to select between multiple values of the same type and dig.As to expose concrete implementations only through interfaces.DryRun(true) and get dependency-path error messages when Invoke fails.Use the golang-uber-dig skill to wire an HTTP service where many route constructors automatically contribute handlers into a routes group consumed by a single server constructor, ensuring missing providers fail at startup.
High-intent search queries and answers about installing and using this skill.
Automate Go dependency injection wiring by using a dig.Container at the composition root to safely resolve complex object graphs during application startup. You define constructors that return types and errors, and dig handles lazy, memoized construction so each dependency is built once and reused.
Manage many Go dependencies by embedding dig.In and dig.Out structs within your constructor parameters and results. This allows you to declaratively wire named values, value groups, and optional dependencies using struct tags, keeping construction clean and preventing brittle manual wiring.
Dependency graph validation works by running DryRun(true) on the dig.Container to validate wiring early without executing side-effecting constructors. When Invoke fails, dig provides clear dependency-path error messages to pinpoint missing providers during application startup.
Yes, you can expose concrete Go implementations only through interfaces using the dig.As tag. This disambiguation technique ensures modular boundaries are respected, allowing you to select between multiple values of the same type while preventing direct access to underlying concrete structs.
Prevent per-request values from leaking by creating child scopes from the dig.Container for request, tenant, or module boundaries. This scope-local composition ensures isolated dependency graphs for concurrent executions, keeping request-scoped values contained.
Yes, dependency injection with dig supports testing-friendly DI by allowing you to build fresh containers per test and override providers via decoration. You can validate object graphs without running side-effecting constructors, ensuring reliable and isolated test environments.
JylhisSet up type-safe dependency injection in Go with samber/do.
dmwin72015Wire Go service dependency graphs with uber-go/dig Provide and Invoke.
berksunduriImplement dependency injection in Go using the uber-go/dig library.
QunnnnGenerate compile-time dependency injection code for Go applications using google/wire.