logging-standards

Enforce zap-based structured logging standards in Go services.

Updated Aug 23, 2026

Search Tags:#security #logging #best-practices #zap #structured-logging

Ready to run

npx skills add https://github.com/canopy-network/launchpad --skill logging-standards

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: logging-standards
Source: https://github.com/canopy-network/launchpad/tree/main/.claude/skills/logging-standards
Command: npx skills add https://github.com/canopy-network/launchpad --skill logging-standards

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces structured, level-based logging with zap in Go services, preventing unstructured logs and unsafe data leakage.

Core Features & Use Cases

Zap Structured Logging: Use typed fields for logs.
Log Levels & Context: Standardized levels and contextual metadata.
Sensitive Data Handling: Avoid logging secrets or PII.

Quick Start

Instrument critical paths with logger.Info/Debug and include request IDs.

Frequently Asked Questions about logging-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I implement structured logging in Go services?▼

Structured logging in Go uses typed fields instead of string concatenation. This Skill enforces zap-based logging with dependency-injected loggers, zap field constructors, and contextual metadata like request IDs, ensuring consistent, queryable logs across services.

Why shouldn't I use fmt or standard library logging?▼

fmt and standard library logging produce unstructured text that's difficult to parse and search. Zap structured logging creates machine-readable logs with typed fields, enabling better monitoring, debugging, and compliance with security standards.

What's the best way to handle sensitive data in logs?▼

Never log secrets, API keys, or PII. This Skill enforces practices that exclude sensitive data by design—using structured fields for safe contextual information only and avoiding string interpolation that could leak credentials.

How do I set up dependency injection for loggers in Go?▼

Inject *zap.Logger as a dependency into your services rather than using global loggers. This Skill requires DI-based logger setup, allowing you to configure logging consistently and test services with mock loggers.

What log levels should I use for normal operations and errors?▼

Standardized log levels—Debug, Info, Warn, Error—help filter logs by severity. This Skill enforces level-based logging so normal operations use Info/Debug while errors are captured appropriately, improving observability.

Can I use zap logging with request tracing?▼

Yes. This Skill requires including contextual fields like request IDs and operation identifiers in logs, enabling correlation across service boundaries and integration with distributed tracing systems.