debuggable-by-default

What problem does it solve?

When code fails in production, tracing across HTTP handlers, job runners, DB clients, and external API calls is difficult without consistent telemetry. This skill defines a standard approach to injecting correlation IDs and structured logs so failures are diagnosable without redeployments.

Core Features & Use Cases

• Structured logging: Emit JSON logs at entry, exit, and error with fields like timestamp, level, service, env, version, request_id, component, op, duration_ms, and error.
• Correlation IDs: Generate and propagate a unique request_id across all downstream calls to tie related events together.
• Boundary observability: Instrument HTTP handlers, workers, DB clients, and external API integrations to improve post-mortem analysis and alerting.
• Recovery guidance: Provide actionable recovery context in error logs to speed incident response.

Quick Start

Instrument your code to generate a correlation ID at request entry, propagate it across all down-stream calls, and emit structured logs at every boundary with actionable context.