failure-recovery

To debug code failures systematically, you can classify errors into predefined types like TEST_ASSERTION or BUILD_ERROR, perform root cause analysis using concrete evidence, and generate targeted minimal code repairs to prevent regressions.

Troubleshooting a runtime exception involves classifying the failure, identifying its origin through evidence-based root cause analysis, and applying minimal code changes guided by a retry decision matrix and loop detection to avoid introducing new regressions.

Classifying build errors and lint violations involves categorizing them into predefined types such as BUILD_ERROR or LINT_VIOLATION, which guides you to the specific failing line and suggests a minimal refactoring to address the root cause.

Handling test assertion failures requires classifying the error, analyzing the root cause based on concrete evidence, and utilizing a retry decision matrix with loop detection to ensure efficient resolution or escalation when initial code repairs fail.

This debugging approach works for common failure patterns in brownfield codebases, specifically addressing test assertions, build errors, runtime exceptions, and regressions by classifying them into predefined types for targeted, evidence-based fixing.

You should escalate a code repair when the retry decision matrix and loop detection identify that repeated targeted fixes are not resolving the failure, ensuring efficient resolution by avoiding endless debugging loops.