golang-uber-digImplements dependency injection in Golang using uber-go/dig — reflection-based container, Provide/Invoke, dig.In/dig.Out parameter and result objects, named values, value groups, optional dependencies, scopes, and Decorate. Apply when using or adopting uber-go/dig, when the codebase imports `go.uber.org/dig`, or when wiring an application graph at startup. For higher-level lifecycle and modules, see `samber/cc-skills-golang@golang-uber-fx` skill.
Install via ClawdBot CLI:
clawdbot install samber/golang-uber-digGrade 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 Aug 13, 2026 · audit v1.0
Generated Oct 8, 2026
A developer CLI tool where commands depend on shared configuration, logging, and storage backends. dig wires the graph at startup so each command constructor receives its dependencies, and different backends can be swapped via named values without changing command code.
A Go library that lets consumers register their own constructors alongside library-provided defaults, using dig.In parameter objects and value groups to collect extension points. The library manages the container while callers control lifecycle through Invoke.
Integration test suites that build a dig container per test, providing mocked databases, caches, and HTTP clients via dig.As interfaces. Tests call Invoke with the system under test and assert behavior without touching real infrastructure.
A legacy Go application that already manages its own signal and lifecycle handling adopts dig incrementally to clean up manual wiring in main(). Constructors are registered in the existing composition root, and value groups collect HTTP handlers and background workers.
A batch data processing service where multiple processors, sources, and sinks are registered as value groups with named variants. dig resolves the pipeline graph once per job, and optional dependencies allow degraded operation when certain sinks are unavailable.
Maintain dig-based libraries or frameworks under permissive licenses and monetize through support contracts, consulting, or priority fixes for enterprises adopting the container in production. The free container drives adoption while paid engagements cover integration and architecture reviews.
Operate a SaaS product whose Go backend uses dig to wire per-tenant modules, feature toggles, and integrations. Clean DI keeps tenant-specific constructors isolated, enabling rapid rollout of new modules while charging subscription tiers for advanced capabilities.
A platform engineering group provides a standardized dig-based application scaffold to product teams inside a larger organization, reducing boilerplate and enforcing conventions. Value is measured in developer velocity, with cost savings reallocated from duplicated wiring work.
💬 Integration Tip
Keep the dig container at the composition root (main or app setup) and pass resolved dependencies down as plain arguments to avoid a hidden service locator; prefer interfaces via dig.As and constructor errors as first-class failures.
Scored Nov 11, 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.