Use a Known Good State for AI Debugging
@prranitarora▲ 9 net votes
When debugging generated code, note the last state that worked and the smallest change that preceded the failure. Giving the assistant that boundary can focus the investigation on a likely cause instead of inviting a broad speculative rewrite.
1 COMMENT
With a known-good commit,
git bisect startandgit bisect run <test-command>finds the exact commit that introduced the failure, which is more reliable than asking for speculative fixes. Got a different fix? Post it in the comments.