golang-google-wireCompile-time dependency injection in Golang using google/wire — wire.NewSet, wire.Build, wire.Bind (interface→concrete), wire.Struct, wire.Value, wire.InterfaceValue, wire.FieldsOf, cleanup functions, //go:build wireinject injector files, and generated wire_gen.go. Apply when using or adopting google/wire, when the codebase imports `github.com/google/wire`, or when wiring an application graph at compile time via `wire.Build`. For runtime DI with reflection, see `samber/cc-skills-golang@golang-uber-dig` skill.
Install via ClawdBot CLI:
clawdbot install samber/golang-google-wireGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/samber/cc-skills-golangAudited May 10, 2026 · audit v1.0
Generated Sep 29, 2026
A backend team structures a Go microservice by declaring provider sets for config, Postgres, Redis, and HTTP handlers, then runs `wire ./...` in CI to guarantee the dependency graph compiles before deployment. Because wire generates plain constructor calls in `wire_gen.go`, there is no runtime reflection or container to debug in production.
A payments company uses `wire.Bind` to explicitly map repository interfaces to concrete Postgres implementations, keeping controllers decoupled from storage details across multiple payment processors. Compile-time resolution catches missing dependencies and ambiguous bindings when new implementations are introduced.
An engineering team migrating from a hand-written main function to google/wire breaks initialization into reusable `wire.NewSet` packages (infra, service, handler). Cleanup functions returned by providers ensure database and cache connections close in reverse order during graceful shutdown.
A device-management platform wires brokers, MQTT clients, and telemetry stores through `wire.Struct` field injection and `wire.FieldsOf` to promote configuration fields as graph nodes. The generated `wire_gen.go` is committed so reviewers can inspect exactly how services are constructed.
A HIPAA-conscious health analytics startup uses compile-time DI to assemble ETL workers with explicit `wire.Value` configuration and interface bindings for interchangeable storage backends. Error detection at `wire ./...` prevents runtime failures that would otherwise surface only when a scheduled job first executes.
Maintainers offer google/wire as a free archived open-source library while monetizing enterprise support contracts, migration audits, and training for teams adopting compile-time dependency injection in large Go codebases. The archived status signals stability but still allows paid bug-fix prioritization and consulting.
A platform product uses wire internally to assemble its Go backend services and exposes a hosted CI feature that automatically runs `wire ./...` and fails builds on broken dependency graphs. Customers pay per repository or per build minute for this verification layer.
An agency specializes in Go architecture, using wire to refactor legacy runtime-DI codebases into compile-time graphs and delivering committed `wire_gen.go` reviewers can trust. They sell fixed-scope modernization projects and ongoing retainers for maintaining provider sets across growing services.
💬 Integration Tip
Install the wire CLI with `go install github.com/google/wire/cmd/wire@latest` and run `wire ./...` after every provider graph change, committing the generated `wire_gen.go` as source. Keep provider sets small and use `//go:build wireinject` on injector files so stub functions never compile into the binary.
Scored Sep 29, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.
Use when writing tests, creating test strategies, or building automation frameworks. Invoke for unit tests, integration tests, E2E, coverage analysis, performance testing, security testing.