
Golang Observability
This is a production observability toolkit that treats the five signals (logs, metrics, traces, profiles, and RUM) as a complete system rather than isolated concerns. It pushes structured logging with slog, Prometheus histograms over summaries, OpenTelemetry tracing with context propagation, and environment-toggled profiling. The best part is the opinionated stance: a feature isn't done until it's observable, and it includes migration paths from legacy loggers plus links to awesome-prometheus-alerts for ready-made rules. It's explicit about cost tradeoffs and the high-cardinality label problem that kills Prometheus instances. Use this when you're instrumenting Go services for production and want guardrails that prevent the common mistakes.
- skills.sh installs
- 41.5K
- GitHub stars
- 3.8K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add samber/cc-skills-golang --skill golang-observability --agent claude-codeInstalls into .claude/skills of the current project.
Files
Persona: You are a Go observability engineer. You treat every unobserved production system as a liability — instrument proactively, correlate signals to diagnose, and never consider a feature done until it is observable.
Orchestration mode: Fan out the five signal-specific sub-agents described in Audit mode (metrics, logging, tracing, profiling, RUM) for auditing observability coverage across a codebase, and merge their coverage findings. On Claude Code, use ultracode to opt into multi-agent orchestration explicitly.
Modes:
- Coding / instrumentation (default): Add observability to new or existing code — declare metrics, add spans, set up structured logging, wire pprof toggles. Follow the sequential instrumentation guide.
- Review mode — reviewing a PR's instrumentation changes. Check that new code exports the expected signals (metrics declared, spans opened and closed, structured log fields consistent). Sequential.
- Audit mode — auditing existing observability coverage across a codebase. Launch up to 5 parallel sub-agents — one per signal (metrics, logging, tracing, profiling, RUM) — to check coverage simultaneously.
Sponsors
Details
- Repository
- github.com/samber/cc-skills-golang
- Categories
- Backend & APIs, DevOps & CI/CD, Debugging, Go
- First seen
- Apr 16, 2026
More from samber/cc-skills-golang
All 47- Golang Dependency Management41.4K
- Golang Structs Interfaces41.3K
- Golang Cli41.1K
- Golang Benchmark41K
- Golang Dependency Injection41K
- Golang Popular Libraries41K
- Golang Stretchr Testify40.9K
- Golang Continuous Integration40.9K
- Golang Grpc40.7K
- Golang Samber Lo40K
- Golang Stay Updated40K
- Golang Samber Do39.8K
- Golang Samber Slog39.8K
- Golang Samber Oops39.7K
- Golang Samber Mo39.7K
- Golang Samber Hot39.7K
- Golang Samber Ro39.6K
- Golang Spf13 Cobra38.6K
- Golang Swagger38.6K
- Golang Graphql38.5K
- Golang Google Wire38.3K
- Golang Spf13 Viper38.3K
- Golang Uber Fx38.1K
- Golang Uber Dig38K