audit-logs

Auditing Winston logger usage in TypeScript involves scanning files to identify incorrect log levels and missing metadata. This Skill applies corrections in place and generates per-file reports detailing the applied fixes alongside a final summary.

Enforcing logging conventions for debug, info, warn, and error levels requires scanning TypeScript files to correct improper usage. This Skill audits logger calls, aligns levels with wiki standards, and applies fixes in place while generating a consolidated report.

Preventing sensitive information leaks in Winston audit logs requires verifying that logger calls do not expose confidential data. This Skill checks TypeScript files for leakage and ensures exceptions use the getErrorMessage(error) helper where required.

This logging audit process targets the BlueStack TypeScript framework specifically. It evaluates and corrects Winston logger calls by comparing them directly against the conventions defined in the BlueStack wiki/core/logging.md documentation.

Running an audit on your project folders automatically generates a report of logging convention violations. The process produces per-file findings of incorrect Winston logger usage and concludes with a final consolidated summary of all applied changes.