debug-package

Configure structured debug logging with custom namespaces for LobeHub components.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/alceupassos/hub --skill debug-package-alceupassos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-package
Source: https://github.com/alceupassos/hub/tree/main/.agents/skills/debug-package
Command: npx skills add https://github.com/alceupassos/hub --skill debug-package-alceupassos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The debug-package Skill aids in efficient debugging within the LobeHub ecosystem by providing structured logging and namespace conventions.

Core Features & Use Cases

  • Custom Namespaces: Facilitates clear logging by defining conventions for different components within the LobeHub application.
  • Log Formatting: Offers a set of format specifiers to create consistent and informative log messages.
  • Use Case: When developing LobeHub applications, this Skill helps isolate and diagnose issues in the server, desktop, client, and router components.

Quick Start

Use the debug-package to set up logging for the server component with the command: debug('lobe-server:server').

Frequently Asked Questions about debug-package

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

FAQPage Schema
How do I implement structured logging for LobeHub application components?

Structured logging for LobeHub components is implemented using custom namespaces and format specifiers. By defining conventions like `debug('lobe-server:server')`, you isolate issues across server, desktop, client, and router modules for clear traceability.

What is the best way to isolate debug logs in a LobeHub server environment?

The best way to isolate debug logs is by applying custom namespace conventions. Defining specific namespaces for different LobeHub components filters log output, allowing you to diagnose server or client issues without noise from other modules.

Does LobeHub debugging require knowledge of specific module architecture?

Yes, debugging LobeHub applications requires understanding the debug module usage and LobeHub component architecture. This foundational knowledge ensures you correctly apply namespace conventions and format specifiers to trace issues effectively.

How do I format log messages for consistent troubleshooting in LobeHub?

You format log messages using provided format specifiers to create consistent and informative outputs. This structured approach to log formatting enhances readability and traceability when diagnosing issues within the LobeHub framework.

Can I use custom namespaces for debugging across different LobeHub clients?

Yes, custom namespaces support debugging across various LobeHub clients. You can define specific conventions for server, desktop, client, and router components, ensuring structured and isolated troubleshooting throughout the entire ecosystem.