debug-package
LobeHub debug package and log namespace guide. Use when adding debug() logging, choosing lobe-* namespaces, troubleshooting DEBUG output, localStorage.debug, or log format specifiers.
npx skills add lobehub/lobehub --skill debug-package --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Debug Package Usage Guide ## Basic Usage ```typescript import debug from 'debug'; // Format: lobe-[module]:[submodule] const log = debug('lobe-server:market'); log('Simple message'); log('With variable: %O', object); log('Formatted number: %d', number); ``` ## Namespace Conventions - Desktop: `lobe-desktop:[module]` - Server: `lobe-server:[module]` - Client: `lobe-client:[module]` - Router: `lobe-[type]-router:[module]` ## Format Specifiers - `%O` - Object expanded (recommended for complex objects) - `%o` - Object - `%s` - String - `%d` - Number ## Enable Debug Output ### Browser ```javascript localStorage.debug = 'lobe-*'; ``` ### Node.js ```bash DEBUG=lobe-* npm run dev DEBUG=lobe-* pnpm dev ``` ### Electron ```typescript process.env.DEBUG = 'lobe-*'; ``` ## Example ```typescript // apps/server/src/routers/edge/market/index.ts import debug from 'debug'; const log = debug('lobe-edge-router:market'); log('getAgent input: %O', input); ```
- Basic Usage
- Namespace Conventions
- Format Specifiers
- Enable Debug Output
- Browser
- Node.js
- Electron
- Example
What does the debug-package skill do?
LobeHub debug package and log namespace guide. Use when adding debug() logging, choosing lobe-* namespaces, troubleshooting DEBUG output, localStorage.debug, or log format specifiers.
How do I install it?
Run `npx skills add lobehub/lobehub --skill debug-package --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From lobehub/lobehub, a repository with 81,252 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.