Nestjs Code Review

What it does

This skill automates code reviews for NestJS applications, providing structured feedback categorized by severity: Critical, Warning, and Suggestion. It identifies potential bugs, style inconsistencies, and suggests improvements to enhance backend robustness. The review process is delegated to the nestjs-code-review-expert agent for in-depth analysis of your codebase.

When to use it

• Before merging pull requests to ensure code quality.
• After implementing new features to validate their correctness and adherence to NestJS best practices.
• To verify NestJS decorators, Dependency Injection (DI) patterns, and guard implementations.
• For architecture validation of NestJS modules and providers.
• When reviewing DTOs, pipes, interceptors, and database integration (TypeORM, Prisma, or Drizzle).

Key capabilities

• Categorizes findings by severity: Critical, Warning, Suggestion.
• Validates module organization, including imports, controllers, providers, and exports.
• Checks Dependency Injection patterns and provider scoping.
• Reviews controller HTTP methods, route naming, status codes, DTOs, validation pipes, and OpenAPI decorators.
• Assesses service implementation for proper business logic encapsulation, error handling, and transaction management.
• Evaluates security aspects like guard implementations, authentication/authorization, and input validation.
• Reviews testing coverage and mocking strategies.

Example prompts

• "Review my NestJS code."
• "NestJS code review of the users controller."
• "Check my NestJS service for potential issues."

Tips & gotchas

• Clearly define the scope of files and modules to be reviewed using glob patterns or grep.
• Always verify that Critical and Warning findings have reproducible evidence (file path, line numbers, code snippet) and actionable fixes before finalizing the review. Findings lacking this should be downgraded or removed.