Debugging a database like TursoDB can be tricky. This guide shows you how to find bugs using bytecode comparison, logging, and special tools like ThreadSanitizer and deterministic simulation.
Developers who work on TursoDB or any SQLite-compatible database will find these steps useful. You can compare bytecode from different databases to spot code generation mistakes.
You can also test for threading issues and reproduce crashes with a fixed seed. The guide even covers corruption analysis for WAL files and database integrity problems.
Global
mkdir -p ~/.claude/skills/debuggingProject
mkdir -p .claude/skills/debuggingSource Repository
Azure Diagnosticsmicrosoft/azure-skills
Debug Azure production issues with systematic diagnostics and AI-powered tools
Azure Messagingmicrosoft/azure-skills
Troubleshoot and fix Azure messaging SDK errors for Event Hubs and Service Bus
Use My Browserxixu-me/skills
Work inside your live browser session for real page inspection and debugging
Diagnosemattpocock/skills
A step-by-step debug loop for finding and fixing hard bugs
Diagnosing Bugsmattpocock/skills
Build a tight feedback loop to find any bug fast
Systematic Debuggingobra/superpowers
Find the root cause of every bug before attempting any fix to save time
Safe Debuglllllllama/rigorpilot-skills
Debug deep learning failures safely with conservative diagnosis and minimal patches
Firebase Crashlyticsfirebase/agent-skills
Set up crash reporting for your Android or iOS app with ease