Golang logging
Skill ComeOnOliver/skillshub/skills/HoangNguyen0403/agent-skills-standard/golang-logging
🧠The right skill, one API call. AI agent skills registry with token-efficient skill resolution. 5,000+ skills from 500+ top repos.
npx -y skills add ComeOnOliver/skillshub --skill golang-loggingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Standards for structured logging and observability in Golang. Use when adding structured logging or tracing to Go services. (triggers: go.mod, pkg/logger/**, logging, slog, structured logging, zap)
SKILL.md
1.4 KB, as published. Nobody here has run it
Golang Logging Standards
Priority: P1 (STANDARD)
Principles
- Structured Logging: Use JSON or structured text. Readable by machines and humans.
- Leveled Logging: Debug, Info, Warn, Error.
- Contextual: Include correlation IDs (TraceID, RequestID) in logs.
- No
log.Fatal: Avoid terminating app inside libraries. Return error instead. Onlymainshould exit.
Libraries
log/slog(Recommended): Stdlib since Go 1.21. Fast, structured, zero-dep.- Zap (
uber-go/zap): High performance, good if pre-1.21 or extreme throughput needed. - Zerolog: Zero allocation, fast JSON logger.
Guidelines
- Initialize logger at startup.
- Inject logger or use a global singleton configured at startup (pragmatic choice).
- Use
slog.Attrfor structured data.
References
Anti-Patterns
- No fmt.Println in production: Use slog or zap for structured, leveled logging.
- No log.Fatal in libraries: Return errors; only main() should call os.Exit.
- No unstructured log strings: Include correlation IDs and structured fields via slog.Attr.