debug

Configure namespace-based debug logging for Node.js and browser environments.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kissMyApps-tlm/kissmychat --skill debug-kissmyapps-tlm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/kissMyApps-tlm/kissmychat/tree/main/.agents/skills/debug
Command: npx skills add https://github.com/kissMyApps-tlm/kissmychat --skill debug-kissmyapps-tlm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers often struggle to triage issues and understand runtime behavior in large applications. Centralized, namespace-based logging helps identify where problems originate without noisy output.

Core Features & Use Cases

  • Structured selective logging with the debug library to enable or disable logs per module.
  • Namespace conventions to organize logs across server, client, and tooling components.
  • Troubleshooting workflows: quickly reproduce and trace issues across distributed parts of the system.

Quick Start

Install the debug package, import it in your code, instantiate a logger with a namespace, and enable logs via environment variables for focused debugging.

Frequently Asked Questions about debug

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

FAQPage Schema
How do I set up namespace-based logging in Node.js applications?

Namespace-based logging uses the debug library to organize logs by module. Install the debug package, import it with a namespace identifier, and enable specific namespaces via the DEBUG environment variable to control which logs appear during runtime.

How do I enable or disable logs for specific modules without changing code?

Selective logging activation uses environment variables to toggle namespaces on or off at runtime. Set DEBUG to your namespace pattern (e.g., DEBUG=app:* or DEBUG=app:database) to display only those logs, reducing noise during troubleshooting.

Can I use namespace-based logging in browser environments?

Namespace-based logging works across both Node.js and browser environments with the debug library. Configure namespaces the same way in client-side code to organize and filter logs consistently across your full-stack application.

What's the fastest way to trace where an issue originates in a large application?

Structured selective logging with namespaces lets you enable logs only for specific components or modules, cutting through noise to pinpoint where problems originate. Use namespace conventions to organize logs across server, client, and tooling components.

Do I need additional setup to manage runtime logs across distributed system parts?

Troubleshooting across distributed components requires the debug library and namespace configuration to trace issues end-to-end. Organize namespaces by component (server, client, tools) and enable them via environment variables to reproduce and inspect runtime behavior systematically.

What happens if I don't configure namespaces for my application logging?

Without namespace-based selective logging, applications produce excessive, unfocused output that obscures root causes and slows diagnosis. The debug library with namespace conventions prevents this by letting you control which modules emit logs and at what detail level.