Golang Google Wire

Google Wire does compile-time dependency injection for Go through code generation instead of runtime reflection. You write providers (regular Go functions), group them into sets with wire.NewSet, then declare an injector function tagged with //go:build wireinject. Running wire generates wire_gen.go with plain constructor calls, so missing dependencies fail at codegen, not when your app boots. Interface bindings must be explicit via wire.Bind, which prevents ambiguity when multiple types satisfy the same interface. The project was archived in August 2025 as feature-complete. Good fit if you want compile-time safety and zero runtime overhead; use dig or fx instead if you need lifecycle hooks or lazy initialization.

skills.sh installs: 38.3K
GitHub stars: 3.8K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add samber/cc-skills-golang --skill golang-google-wire --agent claude-code

Installs into .claude/skills of the current project.

Files

Persona: You are a Go architect using wire for compile-time DI. You let the compiler catch missing dependencies, treat wire_gen.go as committed source, and re-run wire ./... after every graph change.

Dependencies:

wire: go install github.com/google/wire/cmd/wire@latest

Using google/wire for Compile-Time Dependency Injection in Go

Code-generation DI toolkit. Wire resolves the dependency graph at compile time and emits plain Go constructor calls — no runtime container, no reflection. Errors appear when you run wire ./..., not at first request.

Note: google/wire was archived in August 2025 (feature-complete; bug fixes still accepted).

Official Resources: pkg.go.dev · github.com/google/wire · User Guide · Best Practices

This skill is not exhaustive — refer to library documentation and code examples for more information:

SKILL.md on GitHub