debugme

You can diagnose a regression without modifying files by running a read-only, evidence-first workflow that returns observations, a root-cause hypothesis, a recommended fix, and verification steps.

Evidence-first debugging is a read-only diagnosis process that analyzes an error message or failing behavior to produce structured observations, a hypothesized root cause, and a verification plan before any changes are made.

To find the root cause of a failing behavior, provide the error message to a read-only diagnosis workflow, which will analyze the evidence and return a hypothesized root cause alongside recommended steps.

Yes, you can investigate suspected breakage using a strictly read-only diagnosis process that explicitly avoids file modifications and delivers evidence-based observations, root cause, and a fix recommendation.

The best way to triage errors without touching code is applying a read-only diagnosis workflow that gathers evidence to output a root-cause hypothesis, recommended fix, and verification steps.

The limitation of a read-only debugging diagnosis is that it only provides observations, root cause, and a recommended fix without actually applying the modifications or verifying the resolution directly in the codebase.