debug

Root cause analysis from a stack trace uses hypothesis-driven debugging to generate and test for-and-against theories. The Skill parses error messages, file paths, and stack frames to build a structured workflow from error capture to fix validation.

Debugging a failing CI pipeline from GitHub Actions is done by passing the CI failure URL to initiate interactive diagnosis. The Skill extracts error data from the CI logs and applies structured hypothesis testing to identify the root cause.

Hypothesis-driven debugging for error logs works by generating potential root-cause hypotheses and evaluating evidence for and against each one. It clusters related errors across interactive sessions to verify the true failure point stepwise.

You can run a test file and automatically diagnose the failure by passing the test file path as an argument. If the test fails, the Skill initiates the interactive root-cause analysis workflow on the resulting output.

Supported failure inputs for root cause analysis include raw test outputs, stack traces, error log files, and GitHub Actions CI failure URLs. Each input type is parsed to extract messages and stack frames for structured diagnosis.

Interactive diagnosis for error analysis should be used when you need stepwise guidance to move from an error excerpt to a verified fix. It guides you through hypothesis generation, clustering, and validation across sessions.