fix-hand

To fix hand analysis errors, you must access the Supabase database to fetch hand snapshots, execute temporary Python debugging scripts to inspect logs, and run verification scripts. This environment allows you to diagnose OCR misparses and action mismatches, apply code fixes, and prevent future regressions.

Fixing incorrect GTO solver output and missing data requires inspecting database queries and execution logs to locate formatting bugs. You set the expected output, correct the parsing code, and add regression test updates to verify the hand snapshot analysis is accurate.

Yes, Supabase database access is required to diagnose AI Poker Wizard hand analysis bugs. The skill extracts stored hand snapshots from the database to compare expected outputs, inspect logs, and execute temporary Python debugging scripts for verifying code fixes and regression tests.

The best way to prevent poker hand analysis regressions is to add regression test updates immediately after applying code fixes. By executing temporary verification scripts against the Supabase snapshot, you ensure the OCR parsing bug is resolved and will not reoccur.

A wrong hero hand display like KdQs indicates an OCR misparse or action mismatch within the hand snapshot. You must run debugging scripts to locate the formatting bug, correct the parsing code, and execute verification scripts to confirm the fix.