Dependency injection in Golang using samber/do — service containers, lifecycle management, scopes, health checks, graceful shutdown, and module organization. Apply when using or adopting samber/do, wh
Install
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add samber/cc-skills-golang --skill golang-samber-do -a cursor -y
Dependency injection in Golang using samber/do — service containers, lifecycle management, scopes, health checks, graceful shutdown, and module organization. Apply when using or adopting samber/do, when the codebase imports github.com/samber/do or github.com/samber/do/v2, or when refactoring manual constructor injection into a DI container.
Questions
How do I install golang-samber-do?
Download skills/golang-samber-do/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does golang-samber-do live?
The publisher keeps it at https://github.com/samber/cc-skills-golang.
Which agents can use golang-samber-do?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.
Dependency injection in Golang using samber/do — service containers, lifecycle management, scopes, health checks, graceful shutdown, and module organization. Apply when using or adopting samber/do, when the codebase imports github.com/samber/do or github.com/samber/do/v2, or when refactoring manual constructor injection into a DI container.
name: golang-samber-do
description: "Dependency injection in Golang using samber/do — service containers, lifecycle management, scopes, health checks, graceful shutdown, and module organization. Apply when using or adopting samber/do, when the codebase imports github.com/samber/do or github.com/samber/do/v2, or when refactoring manual constructor injection into a DI container."
user-invocable: true
license: MIT
compatibility: Designed for Claude Code, Codex or similar harness, and for projects using Golang.
metadata:
author: samber
version: "1.3.2"
openclaw:
emoji: "💉"
homepage:
requires:
bins:
- go
install: []
skill-library-version: "2.0.0"
allowed-tools: Read Edit Write Glob Grep Bash(go:) Bash(git:) Bash(gopls:
paths:
Persona: You are a Go architect setting up dependency injection. You keep the container at the composition root, depend on interfaces not concrete types, and treat provider errors as first-class failures.
Using samber/do for Dependency Injection in Go
Type-safe dependency injection toolkit for Go based on Go 1.18+ generics.
This skill is not exhaustive — refer to library documentation and code examples for more information:
For Go package docs, symbols, versions, importers, and known vulnerabilities, → See samber/cc-skills-golang@golang-pkg-go-dev skill (godig), preferred over Context7 for Go package facts.
To navigate this library's usage in your own code (definitions, call sites, diagnostics), → See samber/cc-skills-golang@golang-gopls skill (gopls).
Context7 remains a fallback for docs not indexed on pkg.go.dev.
Install v2 — v1 is superseded and lacks the generics-based container, scopes, and lifecycle hooks documented below, so v1-era guidance misleads on every API in this skill:
Eager: Created immediately when the container starts
Transient: New instance created on every request
Value: Pre-created value, no instantiation
Provider Functions
Services MUST be registered via provider functions:
type Provider[T any] func(i Injector) (T, error)
Basic Usage
1. Define and Register Services
Follow "Accept Interfaces, Return Structs":
// Register a service (lazy by default)
do.Provide(injector, func(i do.Injector) (Database, error) {
return &PostgreSQLDatabase{connString: "postgres://..."}, nil
})
// Register a pre-created value
do.ProvideValue(injector, &Config{Port: 8080})
// Register a transient service (new instance each time)
do.ProvideTransient(injector, func(i do.Injector) (*Logger, error) {
return &Logger{}, nil
})
// Register an eager service (created immediately at startup)
do.ProvideValue(injector, &Config{Port: 8080})
2. Invoke Services
The container MUST only be accessed at the composition root:
// Invoke with error handling — reserve for call sites outside the DI graph
// (e.g. an HTTP handler that must degrade gracefully instead of crashing)
db, err := do.Invoke[Database](injector)
// MustInvoke panics on error — preferred in providers, recovered by do.Invoke on the parent call
db := do.MustInvoke[Database](injector)
Inside a provider function, always use do.MustInvoke (or MustInvokeAs/MustInvokeNamed/MustInvokeStruct) rather than the error-returning variant:
A provider already returns (T, error), so propagating a dependency failure with do.Invoke costs an extra if err != nil { return nil, err } on every call.
do.MustInvoke panics instead, but samber/do correctly catches and recovers that panic at the enclosing Invoke call and converts it back into a regular error — this recover happens inside the library itself, not in caller code, so MustInvoke is safe to use inside providers.
The failure still surfaces as an error at the composition root, just without the manual boilerplate in every provider.
Depend on interfaces, not concrete types — lets you swap implementations in tests without touching production code
Each service should have one job — services with multiple responsibilities are harder to test and harder to replace
Keep dependency trees shallow — chains beyond 3-4 levels make initialization order fragile and errors harder to trace
Handle errors in provider functions — a silently failing provider creates a broken service that crashes later in unexpected places
Use scopes to organize services by lifecycle — request-scoped services prevent leaks, global services prevent redundant initialization
Use do.MustInvoke* inside provider functions instead of do.Invoke* — samber/do correctly catches and recovers the panic at the outer Invoke call, turning it back into a returned error, so it's safe to use inside providers and you get the same error propagation without the boilerplate
For scopes, lifecycle management, struct injection, and debugging, see Advanced Usage.
For testing patterns (cloning, overrides, mocks), see Testing.
Quick Reference
Registration
Function
Purpose
do.Provide[T]()
Register lazy service (default)
do.ProvideNamed[T]()
Register named lazy service
do.ProvideValue[T]()
Register pre-created value
do.ProvideNamedValue[T]()
Register named value
do.ProvideTransient[T]()
Register new instance each time
do.ProvideNamedTransient[T]()
Register named transient service
do.Package()
Group service registrations
Invocation
Function
Purpose
do.Invoke[T]()
Get service (with error)
do.InvokeNamed[T]()
Get named service
do.InvokeAs[T]()
Get first service matching interface
do.InvokeStruct[T]()
Inject into struct fields using tags
do.MustInvoke[T]()
Get service (panic on error)
do.MustInvokeNamed[T]()
Get named service (panic on error)
do.MustInvokeAs[T]()
Get service by interface (panic on error)
do.MustInvokeStruct[T]()
Inject into struct (panic on error)
Cross-References
→ See samber/cc-skills-golang@golang-dependency-injection skill for DI concepts, comparison, and when to adopt a DI library
→ See samber/cc-skills-golang@golang-structs-interfaces skill for interface design patterns
→ See samber/cc-skills-golang@golang-testing skill for general testing patterns
How do I install golang-samber-do?
Download skills/golang-samber-do/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does golang-samber-do live?
The publisher keeps it at https://github.com/samber/cc-skills-golang.
Which agents can use golang-samber-do?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.