debug-agent

Debug user-reported issues using NDJSON runtime logs and cited evidence.

1|1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/bitsocialnet/bitsocial-web --skill debug-agent-bitsocialnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-agent
Source: https://github.com/bitsocialnet/bitsocial-web/tree/main/.cursor/skills/debug-agent
Command: npx skills add https://github.com/bitsocialnet/bitsocial-web --skill debug-agent-bitsocialnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic evidence-based debugging using runtime logs. Generates hypotheses, instruments code with NDJSON logs, guides reproduction, analyzes log evidence, and iterates until root cause is proven with cited log lines. Use when the user reports a bug, unexpected behavior, or asks to debug an issue.

Core Features & Use Cases

  • Generate 3-5 precise hypotheses about WHY the bug occurs and instrument code with logs to test them in parallel.
  • Reproduce the bug and collect runtime evidence via NDJSON logs for analysis.
  • Iterate with log-driven verification and escalate to fixes only when evidence supports a hypothesis.

Quick Start

Start a debug session, instrument the code with NDJSON logs, reproduce the issue, and review the resulting runtime evidence.

Frequently Asked Questions about debug-agent

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

FAQPage Schema
How do I debug intermittent failures using runtime logs?

Debug intermittent failures by instrumenting code with NDJSON runtime logs to collect evidence, formulating hypotheses, and reproducing the issue to verify the root cause with cited log lines.

What is the best way to find the root cause of a bug across client and server stacks?

Find the root cause of bugs across client and server stacks by generating precise hypotheses, instrumenting code regions with NDJSON logs, and running parallel tests to verify against runtime log evidence.

How do I reproduce a user-reported bug with log evidence?

Reproduce a user-reported bug by adding region-tagged NDJSON instrumentation to the code, triggering the behavior, and analyzing the collected runtime logs to prove the exact failure point.

Can I use NDJSON logs to debug performance regressions?

You can debug performance regressions using NDJSON logs by instrumenting the code to capture runtime timing data, reproducing the slow behavior, and iterating on log evidence to isolate the bottleneck.

Does evidence-based debugging work without adding dependencies?

Evidence-based debugging requires no external dependencies, relying solely on inserting NDJSON runtime logs into your codebase to generate hypotheses and verify the root cause through cited log lines.