Nestjs performance logging
Skill dkmqflx/nestjs-best-practices-plugin/plugins/nestjs-best-practices/skills/nestjs-performance-logging
Claude Code plugin: 12 NestJS best-practice skills (90 rules) grounded in the official NestJS docs
npx -y skills add dkmqflx/nestjs-best-practices-plugin --skill nestjs-performance-loggingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
NestJS performance and logging/observability best practices. Use when optimizing a NestJS app's throughput or adding structured logging, health checks, or graceful shutdown. Triggers on FastifyAdapter, compression, pino logger, health checks, Terminus, or graceful shutdown.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.9 KB, as published. Nobody here has run it
NestJS Performance & Logging
Practical rules for squeezing throughput out of a NestJS app and making it observable in production: structured logs, correlation IDs, health checks, and clean shutdown.
When to Apply
- Optimizing request throughput or latency of a NestJS HTTP service
- Replacing
console.logwith production-grade structured logging - Running in Kubernetes/ECS where readiness/liveness probes and graceful drain matter
- Tracing requests across services or debugging incidents from logs
- Hardening logs so secrets, tokens, and PII never leak
Rules
fastify-adapter-for-throughput- Prefer FastifyAdapter over Express for higher throughput.enable-compression- Gzip response payloads to cut bandwidth and latency.structured-json-logging- Use nestjs-pino for structured JSON logs instead of console.log.avoid-request-scoped-providers- REQUEST scope re-instantiates per request; keep singletons.graceful-shutdown-hooks- enableShutdownHooks + OnModuleDestroy to drain cleanly.health-checks-terminus- Expose @nestjs/terminus health/readiness endpoints for orchestrators.correlation-ids- Propagate a request/correlation ID through every log line.dont-log-sensitive-data- Redact secrets, tokens, and PII from logs.
How to Use
Load this skill when working on NestJS performance or observability. Skim the Rules index, open the relevant rules/<name>.md for the why plus an incorrect/correct code pair, and apply the pattern. Rules are tagged by impact (CRITICAL/HIGH/MEDIUM/LOW) so you can prioritize.