omk-test-debug-loop

Fix failing lint, typecheck, or build commands by capturing the exact command output, classifying the failure type, and applying a minimal root-cause fix. Re-run the failing command to verify the change while maintaining strict test and type integrity.

Debug test failures by converting command output into a classified failure category like syntax, type, dependency, or flaky. This classification prevents guessing and guides you to identify the smallest related file set for a targeted root-cause fix.

Triage CI build failures by capturing the exact failing command output and transforming it into a classified, structured report. This process isolates the underlying error and generates a verifiable sequence of targeted fixes rather than patching symptoms.

Yes, automated debugging suits iterative development requiring minimal changes by selecting the smallest related file set. After applying a fix, it re-runs the failing command and adjacent checks, stopping with a blocker report if repeated failures occur.

Your debugging loop may repeatedly fail because symptom patches are applied instead of root-cause fixes. Classify the exact error, target the smallest file set, re-run the command, and stop with a blocker report if failures persist to avoid endless loops.

Yes, this debugging approach works for both local development and CI triage. It requires capturing the exact failing command and output, classifying the failure, and providing a structured report for the re-run result to verify the fix.