Description
debug is an agent skill from the LobeHub repository that explains how to add debug logging with the debug package. It is for code that needs to write diagnostic output which can be turned on per area. The skill shows the basic pattern: import debug, create a logger with a namespace, then call it with a message or with format placeholders such as %O for objects and %d for numbers. It sets out the namespace convention the project uses, in the form lobe-[module]:[submodule], so that each logger can be switched on or off by name. The skill is useful when you add logging to a new module, when you need to understand which log namespaces already exist, or when you are implementing a debugging feature. It is a short reference rather than a full guide to the logging stack, so it does not cover how the logs are collected or shipped. Because it is about a single package, it is a quick aid for contributors working in the monorepo. It passes Gen Agent Trust Hub, Socket and Snyk on skills.sh. Install it with npx skills add https://github.com/lobehub/lobehub --skill debug.…
Highlights
- Shows how to create debug loggers with a namespace
- Explains the lobe-[module]:[submodule] namespace convention
- Covers %O and %d format placeholders
- Quick reference for contributors in the monorepo
Ratings & Reviews
No ratings yet
Be the first to rate debug.
People also visit
debug FAQ
What package does it cover?
The debug logging package, used with a namespace per module.
What is the namespace format?
lobe-[module]:[submodule], for example lobe-server:market.
How do I log an object?
Use the %O placeholder in the format string, which the skill's example shows with a log call.
How do I install it?
Run npx skills add https://github.com/lobehub/lobehub --skill debug.
Which security audits does it have?
On skills.sh, Gen Agent Trust Hub, Socket and Snyk all pass.
What are the best debug alternatives?
Popular alternatives to debug include add-provider-doc, add-setting-env and desktop. See all debug alternatives