debug-agent

Debug software by instrumenting NDJSON logs and testing hypotheses with cited evidence.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/kaissalha/webld --skill debug-agent-kaissalha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-agent
Source: https://github.com/kaissalha/webld/tree/main/.agents/skills/debug-agent
Command: npx skills add https://github.com/kaissalha/webld --skill debug-agent-kaissalha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Debugging complex issues often relies on static code review, which misses real-world runtime data. This Skill enables evidence-based debugging by instrumenting code with NDJSON logs, generating hypotheses, and guiding reproduction using cited log evidence to validate root causes.

Core Features & Use Cases

  • Generate 3-5 precise hypotheses about why a bug occurs to structure investigation.
  • Instrument code with runtime logs and analyze evidence to confirm or reject hypotheses.
  • Guide users through reproducible steps and verify fixes with post-run logs.
  • Iteratively refine the investigation until root cause is proven with logged evidence.

Quick Start

Start by enabling runtime instrumentation and NDJSON logging to generate and test hypotheses against live evidence.

Frequently Asked Questions about debug-agent

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

FAQPage Schema
How do I use runtime logs to find the root cause of a software bug?

Evidence-driven debugging uses instrumented NDJSON runtime logs to generate hypotheses and verify root causes. You collect structured execution data during reproduction to systematically prove or reject potential failure points.

What is hypothesis-driven debugging and how does it work with NDJSON logs?

Hypothesis-driven debugging structures investigation by formulating 3-5 precise theories about a bug. You instrument code with NDJSON logs to capture runtime evidence, confirming or rejecting each hypothesis based on cited log output.

How do I debug performance regressions using runtime instrumentation?

Debug performance regressions by enabling runtime instrumentation and NDJSON logging to capture live execution metrics. This structured evidence guides reproduction and helps verify the exact root cause of the unexpected behavior.

Can I use structured logging to verify software fixes across web apps and services?

Yes, structured NDJSON logging verifies software fixes by comparing post-run logs against initial runtime evidence. This iterative process proves the root cause is resolved by checking cited evidence from the instrumented code.

Does evidence-based debugging work without adding dependencies or components?

Yes, this approach requires no external dependencies or components. It relies solely on instrumenting your existing codebase with NDJSON runtime logs to collect evidence and validate hypotheses for root-cause analysis.

What is the best way to reproduce unexpected behavior using structured logs?

The best way to reproduce unexpected behavior is guiding through reproducible steps while capturing runtime logs. NDJSON instrumentation provides the cited evidence needed to validate hypotheses and iteratively refine the investigation.