Standardize structured application logging with Pino-shaped APIs and FakeLogger assertions.
npx skills add https://github.com/johinsDev/loyalty-app --skill log-johinsdev
Please help me install this Agent Skill. Skill: log Source: https://github.com/johinsDev/loyalty-app/tree/main/.claude/skills/log Command: npx skills add https://github.com/johinsDev/loyalty-app --skill log-johinsdev
It prevents scattered, inconsistent logging and makes logs testable and extensible across every app and package in the monorepo.
Use the log manager exported by your app bootstrap module and log structured events using bindings (objects) and messages (strings) instead of console.log.
High-intent search queries and answers about installing and using this skill.
Standardize structured logging by using a process-wide LogManager singleton with swappable channels, providing a consistent Pino-shaped API for tRPC, Next.js route handlers, and server actions. This prevents scattered, inconsistent logs across your services and packages.
Test application log output deterministically by using the logManager.fake() method to capture records. This FakeLogger implementation allows you to assert on log levels, messages, bindings, and errors without relying on actual console output.
Attach request and tenant identifiers to structured logs using the child() method for scoped context. This allows you to attach specific bindings to log records without mutating shared logger instances across different requests or jobs.
Yes, this structured logging approach explicitly supports Trigger.dev jobs. The LogManager abstraction applies consistently across request handling, server actions, and background jobs, ensuring uniform observability and context scoping throughout your asynchronous workflows.
Yes, you can use Pino-shaped APIs for bindings and errors. The logging abstraction provides a single consistent API built on Pino-backed structured logs, featuring built-in console and silent channels for flexible output management.
You need a process-wide LogManager singleton to centralize logging configuration and enable swappable channels. This ensures all packages and services in the monorepo query, test, and extend logs consistently without scattered or conflicting logger instances.
LeadGrowGTMInitialize Trigger.dev projects by creating trigger.config.ts and task directories.
princegarg001Configure Pino structured logging for Node.js applications with colorized development and JSON production output.
saeed-vayghanCorrelate logs, traces, and metrics to diagnose root causes in distributed systems.
petbrainsConfigure structured JSON logging for Node.js backends with redaction and request tracing.
