forge-logging

What problem does it solve?

Most application logging is unreliable for incident response: it lacks structure, correlation IDs, consistent event names, and often leaks secrets, making failures hard to reproduce and analyze.

Core Features & Use Cases

• Structured JSON-first logging: Ensure every log line is a parseable JSON object suitable for log aggregation, filtering, and alerting.
• Correlation and tracing: Attach request_id (and trace_id/span_id where applicable) so logs can be tied to a single request path across services.
• Redaction and safe error handling: Redact secrets at the logger so Authorization tokens and credential-like strings never reach storage, and log errors with full error objects and correct severity boundaries.
• Use case: When adding or refactoring logging in a backend service, ensure logs support on-call debugging, audits/retention separation, and verifier-enforced discipline against unsafe patterns like console.log or templated messages.

Quick Start

Use the forge-logging skill to enforce structured JSON logging with request correlation IDs and redaction for any backend service codebase.