debug

Collect structured runtime logs into per-session files for debugging Node.js or browser projects.

11.9k|1.5k|Updated Jul 12, 2023

Search Tags:#debugging #Node.js #instrumentation #server-side #log-analysis #hypothesis-testing #runtime-logs

Ready to run

npx skills add https://github.com/elie222/inbox-zero --skill debug-elie222

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/elie222/inbox-zero/tree/main/.claude/skills
Command: npx skills add https://github.com/elie222/inbox-zero --skill debug-elie222

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging complex issues often requires collecting runtime evidence from the running system, reproducing conditions, and manually logging outputs. This Skill automates log collection to provide server-side evidence, reducing back-and-forth with users and speeding up fixes.

Core Features & Use Cases

Automated runtime logging: captures structured logs during bug reproduction, with session management for organized analysis.
Guided workflow: provides a multi-phase process (start server, create session, instrument, reproduce, analyze, fix, verify, optional five whys) to ensure reproducibility.
Safe, auditable data: stores logs locally in a per-session file for review and verification without exposing user secrets.
Quick-start oriented: ideal for developers who need deterministic evidence when debugging.

Quick Start

Start the log server for your project: node scripts/debug_server.js /path/to/project
Create a session: curl -s -X POST http://localhost:8787/session -d '{"name":"debug-session"}'
Post log messages: curl -s -X POST http://localhost:8787/log -d '{"sessionId":"debug-session-abcdef","msg":"Function entry","data":{}}'
Reproduce the bug in your app and review the generated log file at .debug/debug-debug-session-abcdef.log

Frequently Asked Questions about debug

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

FAQPage Schema

How do I collect server-side runtime logs to debug Node.js bugs?▼

You can collect server-side runtime logs by starting a local debug server and creating a session to capture structured log payloads. This provides deterministic evidence during bug reproduction without requiring manual user prompts.

What is the best way to diagnose timing issues and nulls in a Node.js application?▼

Diagnosing timing issues and nulls is best handled through automated runtime instrumentation and structured log analysis. This approach captures per-session evidence locally, enabling systematic hypothesis testing and post-fix verification.

How do I set up structured log payloads for bug reproduction analysis?▼

To set up structured log payloads, start the log server, create a session via HTTP POST, and send log messages with associated data. The session stores these payloads locally in a dedicated file for organized review.

Does this automated logging workflow work with browser-based projects?▼

Yes, the automated logging workflow works across any Node.js or browser-based project. It applies during bug investigations involving complex user interactions, capturing runtime evidence safely without exposing user secrets.

Can I use session management to organize runtime logs for post-fix verification?▼

Yes, you can use session management to organize runtime logs for post-fix verification. The guided workflow creates a unique session file for each reproduction attempt, ensuring logs remain auditable and separated for analysis.

What are the limitations of manual log analysis for complex user interactions?▼

Manual log analysis for complex interactions often requires reproducing conditions and manually logging outputs, causing excessive back-and-forth. Automating this collection provides server-side evidence directly, reducing delays and speeding up fixes.