agent-debugger

To find the root cause of a failing test, provide the stack trace and codebase context to generate a structured diagnosis. The analysis forms staged hypotheses and gathers evidence to pinpoint the bug without applying code changes.

Debugging CI failures without modifying the codebase involves analyzing test outputs and error messages to produce a concise fix brief. This approach delivers actionable engineering decisions and a proposed fix rather than implementing the solution directly.

You can diagnose bugs using error messages and reproduction steps, but providing relevant code references improves the diagnosis. The analysis reads bug reports and test outputs to guide engineering decisions and generate a precise fix brief.

Performing a root-cause analysis for local debugging sessions requires providing failing test details and relevant code context. The process applies staged hypothesis formation and evidence gathering to deliver a structured diagnosis and proposed fix.

This debugging approach does not automatically implement the proposed fix brief. It reads bug reports and test outputs to diagnose the root cause and generate a concise fix brief, leaving the actual code changes to the developer.

Providing context like reproduction steps is required for a bug diagnosis because the analysis relies on error messages and relevant code references. This context enables the structured diagnosis to form accurate hypotheses and deliver actionable guidance.