Nestjs Code Review
ListedAutomates NestJS code reviews, identifying potential bugs, style inconsistencies, and suggesting improvements for robust backends.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add giuseppe-trisciuoglio/developer-kit --skill nestjs-code-review -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
giuseppe-trisciuoglio
Taken from the source listing. We haven't verified who controls this account.
Install target
Live repository
Not pinned. Installing fetches whatever the repository holds at the time you run the command.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: api.sendgrid.com.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
Hosts contacted
api.sendgrid.comundeclaredWhat it found
- plugins/developer-kit-typescript/skills/nestjs-code-review/references/anti-patterns.md:77contacts api.sendgrid.com
const response = await fetch('https://api.sendgrid.com/v3/mail/send', {
Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned giuseppe-trisciuoglio/developer-kit at fe73fb33a0.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- fe73fb33a0
- Scanned
- 4 files, 821 lines
About this skill
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.