Back to Skills

full-stack-debugger

This skill should be used when debugging full-stack issues that span UI, backend, and database layers. It provides a systematic workflow to detect errors, analyze root causes, apply fixes iteratively, and verify solutions through automated server restarts and browser-based testing. Ideal for scenarios like failing schedulers, import errors, database issues, or API payload problems where issues originate in backend code but manifest in the UI.

6starsUpdated 3/3/2026

Security Assessment

High Risk(40/100)

Detected risks:

Destructive Operations([SKILL.md] rm -rf, [README.md] rm -rf)
Security Score40/100

About full-stack-debugger

The Full Stack Debugger skill is designed to help developers systematically identify and resolve issues across the entire application stack, including the UI, backend, and database layers. It addresses common problems such as failing schedulers, import errors, database issues, or API payload problems, where errors originating from the backend manifest in the user interface. This skill provides a structured debugging workflow that guides developers through each stage of issue resolution, from detection to verification, ensuring a thorough and efficient debugging process.

FAQ

When should I trigger the Full Stack Debugger skill?

You should trigger this skill when encountering errors in the UI, backend logs, database state, or API responses. It is particularly useful for issues like task execution failures, database errors, API payload issues, or cascading failures across multiple components.

Does the Full Stack Debugger skill work with all programming languages?

While this skill is versatile, it primarily targets full-stack applications, including both frontend (UI) and backend (API/Database) components. The specific languages and technologies used should align with the skill's detection and analysis tools (e.g., browser dev tools, backend logs, sqlite3).

What are the key requirements for using the Full Stack Debugger?

To use this skill effectively, you will need access to the relevant application logs, a working environment with the ability to query databases (such as sqlite3), and knowledge of your system's structure to identify error patterns. Additionally, you'll need access to browser dev tools for UI error detection.

All Files

2 files
SKILL.md10.1 KB
View
README.md10.5 KB
View

Install full-stack-debugger

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

ingpoc/SKILLS