debug

Create and emit namespaced log messages with the debug package.

Updated Mar 2, 2026

Search Tags:#debugging #logging #diagnostics #instrumentation #nodejs #namespaces

Ready to run

npx skills add https://github.com/Staysr/lobe-windos-build --skill debug-staysr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/Staysr/lobe-windos-build/tree/main/.agents/skills/debug
Command: npx skills add https://github.com/Staysr/lobe-windos-build --skill debug-staysr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging and observability for code paths using the debug package, enabling structured, namespace-scoped logs across modules.

Core Features & Use Cases

Lightweight, namespaced debugging for Node.js, browser, and Electron environments
Demonstrates standard usage patterns with the debug library and common namespace conventions
Use cases include diagnosing issues in server or client code and tracing execution across modules

Quick Start

Run a namespaced logger and emit messages to verify your log output.

Frequently Asked Questions about debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I implement namespaced logging for Node.js debugging?▼

Namespaced logging organizes debugging output by applying the debug package to create and emit scope-specific log messages across modules. This allows you to filter trace output by namespace during development and troubleshooting tasks.

Does namespaced debugging work across browser and Electron environments?▼

Yes, namespaced debugging works across Node.js, browser, and Electron environments. The debug package provides cross-environment compatibility, allowing you to trace execution and diagnose issues consistently whether in server or client code.

What is the best way to trace execution across modules during troubleshooting?▼

The best way to trace execution across modules is using namespaced log messages. By assigning named namespaces to different modules, you can dynamically enable or disable specific debug scopes to isolate issues without flooding your console with irrelevant output.

How do I set up standard usage patterns with the debug library?▼

Standard usage patterns with the debug library involve creating a namespaced logger instance and emitting messages to verify log output. You apply common namespace conventions to structure your debugging output for fast and efficient diagnostics.

When do I need namespaced log messages for diagnostics?▼

You need namespaced log messages when diagnosing issues across multiple modules or environments. Namespace-scoped logs provide structured observability, enabling you to selectively trace specific code paths without modifying core application logic.

Why use namespaced debugging instead of standard console logging?▼

Namespaced debugging provides lightweight, structured output that can be toggled by environment variables, unlike standard console logging. This approach prevents log flooding and allows precise tracing across modules, significantly improving troubleshooting efficiency.