Skip to content
cccskills
FreePublished on GitHub

golang-logging

Standards for structured logging and observability in Golang. Use when adding structured logging or tracing to Go services.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (3)

  • SKILL.md2.5 KB
  • evals/evals.json1.9 KB
  • references/slog-patterns.md1.3 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Golang Logging Standards

Priority: P1 (HIGH)

Principles

  • Structured Logging: Use JSON or structured key-value attributes. Machine-readable and filterable.
  • Strict Single-Log Boundary: Log errors once where they are handled or translated at the boundary (service or handler level). Never double-log in repository, utility, or deep helper functions—wrap and return errors instead.
  • Typed Context Keys: Always use private typed keys (type ctxKey string) for storing and retrieving request-scoped logger attributes.
  • Business Traceability vs PII Redaction: Include non-sensitive business identifiers (e.g. tenant ID, organization code, order number) for traceability. Strictly redact credentials, API tokens, passwords, and sensitive PII.
  • Leveled Logging: Debug, Info, Warn, Error.
  • No log.Fatal: Avoid terminating apps inside libraries. Return errors instead; only main() should handle process exit.

Libraries

  • log/slog (Recommended Stdlib): Stdlib since Go 1.21. Fast, structured, zero-dep.
  • Zap (uber-go/zap): Production-grade structured logger for high-throughput microservices.
  • Zerolog: Zero allocation, fast JSON logger.

Workflow: Set Up Structured Logging

  1. Initialize structured logger at startup in main() with standard JSON output.
  2. Inject request correlation IDs (TraceID, RequestID) via middleware using typed context keys.
  3. Pass logger via context (logger.FromContext(ctx)) or constructor injection.
  4. Log at the application boundary on error; wrap errors upstream without intermediate logging.

See slog setup and usage examples

Anti-Patterns

  • No Double-Logging: Do not log an error in the repository/database helper AND log it again in the service/handler.
  • No fmt.Println in production: Use structured, leveled loggers.
  • No Untyped Context Keys: Avoid context.WithValue(ctx, "logger", l) with raw string keys.
  • No Secrets in Logs: Redact bearer tokens, passwords, and sensitive personal info.
  • No log.Fatal in libraries: Return errors; only main() should call os.Exit.

References

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their specific skills.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test recipes to their specific skills.

The English summary is being prepared. Showing the original description.

HoangNguyen0403/agent-skills-standard581Updated Oct 24, 2026

See all skills by HoangNguyen0403

Report a problem with this skill