golang-spf13-viperGolang configuration library using spf13/viper — layered precedence (flag > env > file > KV > default), BindPFlag/BindPFlags, SetEnvPrefix + SetEnvKeyReplacer + AutomaticEnv, ReadInConfig + ConfigFileNotFoundError, Unmarshal + mapstructure struct tags, Sub for sub-trees, WatchConfig + OnConfigChange for hot reload, viper.New() for test isolation, and remote KV integration. Apply when using or adopting spf13/viper, or when the codebase imports `github.com/spf13/viper`. For CLI command structure alongside viper, see the `samber/cc-skills-golang@golang-spf13-cobra` skill. For general CLI architecture, see `samber/cc-skills-golang@golang-cli`.
Install via ClawdBot CLI:
clawdbot install samber/golang-spf13-viperGrade 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 24, 2026 · audit v1.0
Generated Aug 10, 2026
In a microservices architecture, each service needs to load configuration from multiple sources like environment variables, config files, and defaults. Viper's layered precedence ensures that service-specific overrides (via env vars) take precedence over shared config files, enabling flexible deployment across different environments.
A command-line tool that requires both command-line flags and a user-specific config file. Viper allows binding flags to configuration keys, so users can set a value via a flag, which overrides the config file, while still allowing defaults for optional settings. This simplifies user experience and reduces configuration errors.
A long-running daemon or service that needs to pick up configuration changes without restarting. Viper's WatchConfig and OnConfigChange enable hot reload, allowing operators to update configurations dynamically, reducing downtime and improving operational flexibility.
Applications deployed across development, staging, and production environments often need different settings. By using Viper's env prefix and replacer, teams can externalize environment-specific configurations via environment variables, while keeping a base config file for common settings. This simplifies deployment and reduces the risk of misconfiguration.
Offer a SaaS product where configuration management is a core feature. Use Viper to manage multi-tenant configurations, allowing different tiers to have different default settings that can be overridden by tenant-specific environment variables. This enables flexible plans while maintaining a single codebase.
Provide a CLI tool or library that simplifies configuration management for developers. Offer a free version with basic features, and a premium version with advanced features like remote KV integration or hot reload. This can attract a wide user base while monetizing advanced capabilities.
Offer consulting services to help enterprises implement robust configuration management using Viper in their Go applications. This includes architecture reviews, code implementation, and best practices training. Monetize through project-based fees or hourly consulting charges.
💬 Integration Tip
Ensure to set env prefix, key replacer, and automatic env together at application startup to avoid common pitfalls with nested keys. Bind flags in init or PersistentPreRunE, and always handle ConfigFileNotFoundError gracefully.
Scored Aug 10, 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.