Skip to content
TrustedSkillsbeta
Back to all skills

Debug:Nestjs

Checked
snakeo·vlatest·backend

Identifies and suggests fixes for common errors in NestJS applications using advanced code analysis.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add snakeo/claude-debug-and-refactor-skills-plugin --skill debug:nestjs -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

snakeo

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • 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 undeclared network calls: passed

    Makes no network calls.

    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.

  • 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 snakeo/claude-debug-and-refactor-skills-plugin at e2e79df88e.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
e2e79df88e
Manifest
plugins/debug-and-refactor/skills/debug-nestjs/SKILL.md
Scanned
1 file, 684 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill assists in debugging NestJS applications. It can analyze error messages, identify potential causes of issues within the NestJS framework, and suggest code modifications to resolve problems. The skill is designed to help developers quickly diagnose and fix bugs in their NestJS projects.

When to use it

  • You're encountering unexpected errors in your NestJS application and need assistance understanding the root cause.
  • You’ve received a stack trace from a failing test and want help interpreting it within the context of your NestJS code.
  • You are refactoring existing NestJS code and want to ensure no new bugs are introduced during the process.
  • You're struggling with a complex error related to dependency injection or module configuration in your NestJS project.

Key capabilities

  • NestJS Error Analysis
  • Code Suggestion for Bug Resolution
  • Dependency Injection Troubleshooting
  • Module Configuration Assistance

Example prompts

  • "I’m getting this error: TypeError: Cannot read property 'name' of undefined. Can you help me debug it in my NestJS application?"
  • "Here is the stack trace from my failing test. What could be causing this issue in my controller?"
  • “My NestJS module isn't loading correctly. Can you review its configuration and suggest fixes?”

Tips & gotchas

The skill’s effectiveness relies on providing clear error messages or relevant code snippets for analysis. Ensure the provided context is sufficient for accurate debugging suggestions.