winston-logging-on-change

To add Winston logging to changed NestJS backend code, this Skill integrates concise, contextual logs around important branch decisions and failures in modified controllers, services, and handlers. It requires pre-existing Winston wiring and a shared LoggerService to maintain project conventions.

Preventing sensitive data exposure in Winston logs is handled by enforcing strict exclusion of secrets, tokens, raw request bodies, and PII. The Skill automatically standardizes safe logging practices across modified backend components.

Yes, this Winston logging approach works with existing NestJS LoggerService conventions. It requires pre-existing Winston wiring and actively adheres to your project's established logger conventions when repairing logs in modified guards, interceptors, and strategies.

Improving observability in modified NestJS backend code is best achieved by adding high-signal Winston logs around important outcomes and failures. This Skill standardizes logging quality specifically in changed files to enhance backend monitoring without exposing sensitive payloads.

Yes, you need pre-configured Winston wiring to use this NestJS logging feature. The Skill focuses on adding and repairing logging in changed code and requires an existing shared LoggerService rather than setting up Winston from scratch.