When your Turso queries aren't behaving like SQLite, this gives you the full debugging arsenal. The bytecode comparison workflow is the standout here: EXPLAIN your query in both engines, compare the output, and you'll know immediately if the bug is in code generation or deeper in the VM. Beyond that, you get ThreadSanitizer stress tests for concurrency bugs, deterministic simulation with seeds for reproducing flaky failures, and corruption analysis tools for WAL issues. The logging can dump megabytes per test run, so use it surgically. If you're working on database internals or chasing subtle compatibility issues, these tools will save you days of blind debugging.
npx skills add https://github.com/tursodatabase/turso --skill debugging