debug-agent

Instrument code with NDJSON logs to debug issues via hypothesis testing.

3.5k|155|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/millionco/expect --skill debug-agent-millionco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-agent
Source: https://github.com/millionco/expect/tree/main/.agents/skills/debug-agent
Command: npx skills add https://github.com/millionco/expect --skill debug-agent-millionco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables rapid, evidence-based debugging by collecting runtime logs, forming hypotheses, and guiding reproducible investigations to identify root causes without guessing.

Core Features & Use Cases

  • Instrument runtime code with lightweight NDJSON logs to capture hypotheses and outcomes.
  • Generate 3-5 precise hypotheses per bug report and evaluate them in parallel using live data.
  • Provide a structured reproduction plan and evidence-backed conclusions to engineers for quick fixes.
  • Use post-fix verification to confirm that observed issues are resolved and instrumentation can be removed safely after proof.

Quick Start

Start a debugging session by running the agent with a reproducible bug and let the system generate runtime logs to begin the evidence-based loop.

Frequently Asked Questions about debug-agent

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

FAQPage Schema
How do I debug a user-reported issue using runtime logs instead of guessing?

Evidence-based debugging with runtime logs gathers in-session data to systematically identify root causes without guessing. It instruments code with lightweight NDJSON logs, generates 3-5 hypotheses per bug report, and evaluates them in parallel against live data to prove the root cause.

How do I find the root cause of a bug by testing hypotheses with NDJSON logs?

Finding a root cause with NDJSON logs involves generating 3-5 precise hypotheses per bug report and evaluating them in parallel using live runtime data. The process enforces phased hypothesis testing and verifiable proof before applying fixes, iterating until the root cause is proven with cited log lines.

What is the best way to systematically reproduce a bug and verify the fix?

The best way to systematically reproduce a bug is to use a structured reproduction plan supported by runtime log instrumentation. After evaluating hypotheses and applying fixes, post-fix verification confirms the issue is resolved, ensuring instrumentation can be removed safely only after proof is established.

How do I add instrumentation to capture runtime logs for debugging across components?

To capture runtime logs for debugging across components, instrument your runtime code with lightweight NDJSON logs. This strict instrumentation records hypotheses and outcomes during an in-session investigation, providing verifiable evidence and cited log lines to guide reproducible debugging.

Can I use automated hypothesis generation for debugging reproducible bugs?

Yes, you can use automated hypothesis generation for debugging reproducible bugs. The system automatically generates 3-5 precise hypotheses per bug report and evaluates them in parallel using live data captured from in-session runtime logs, enforcing verifiable proof before applying fixes.