Configure structured JSON logging with slog in Go projects.
npx skills add https://github.com/air-gapped/cooked --skill logging-config
Please help me install this Agent Skill. Skill: logging-config Source: https://github.com/air-gapped/cooked/tree/main/.claude/skills/logging-config Command: npx skills add https://github.com/air-gapped/cooked --skill logging-config
This skill standardizes logging across Go applications by enforcing the use of slog with structured fields, replacing ad-hoc logging patterns like fmt.Printf or log.Printf to produce consistent, machine-readable logs.
High-intent search queries and answers about installing and using this skill.
To set up structured logging in Go using slog, initialize a global JSON logger at program startup that writes to stdout. Replace ad-hoc patterns like log.Printf with slog methods using structured key-value fields for machine-readable output.
You should use slog instead of log.Printf because slog enforces structured, machine-readable JSON logging with consistent key-value pairs. This standardization significantly improves observability and simplifies debugging across Go services compared to unstructured text output.
The best way to standardize logs across multiple Go services is to enforce a single, centralized slog logger initialization pattern at startup. This ensures all services emit consistent, JSON-formatted structured fields for monitoring and debugging.
Yes, you can configure a centralized slog logger at program startup using a JSON handler. This single initialization pattern ensures that all subsequent logs emit with consistent, structured key-value fields instead of variable ad-hoc text.
To replace fmt.Println with structured fields in Go, initialize a slog JSON handler at startup and call slog methods like slog.Info with key-value pairs, such as slog.Info("request processed", "method", "GET"), to produce machine-readable logs.
You need JSON formatted logs in Go applications when services require consistent, machine-readable output for monitoring and debugging. Structured slog logging replaces unstructured text to improve observability and enable automated log analysis.
dmwin72015Compose samber/slog pipelines for sampling, sanitizing, and routing Go logs.
DoubleslashSEParse infrastructure logs to extract actionable insights for incident detection.
shafibabarImplement Go structured logging with slog, trace correlation, and PII redaction.
Mte90Define structured logging standards for Golang applications using log/slog or uber-go/zap.
