Compare bytecode, logs, and sanitizer outputs to debug Turso databases.
npx skills add https://github.com/tursodatabase/turso --skill debugging-tursodatabase
Please help me install this Agent Skill. Skill: debugging Source: https://github.com/tursodatabase/turso/tree/main/.claude/skills/debugging Command: npx skills add https://github.com/tursodatabase/turso --skill debugging-tursodatabase
This Skill helps developers debug Turso databases by comparing bytecode, analyzing logs, and using ThreadSanitizer and deterministic simulation tools to identify root causes of behavior differences and corruption scenarios.
Run a basic diagnostic by launching the Turso binary with a memory database and a simple query, for example: cargo run --bin tursodb :memory: 'SELECT 1+1;'
High-intent search queries and answers about installing and using this skill.
Debug Turso database bytecode discrepancies by comparing expected and actual bytecode using provided scripts to pinpoint code-generation or VM issues. This process directly identifies inconsistencies within development and QA environments.
ThreadSanitizer surfaces data races and threading bugs in Turso databases by running sanitizers alongside deterministic simulation tools. This replay-driven simulation exposes concurrency issues during reproduction and analysis.
Reproduce WAL and data-corruption scenarios in Turso using guided references and provided scripts for analysis. These tools help investigate corruption by collecting and correlating logs from production-like runs.
Yes, you need access to Turso build artifacts and the ability to run with ThreadSanitizer to execute deterministic simulations. These prerequisites are required to reproduce and analyze failures effectively.
Run a basic diagnostic by launching the Turso binary with a memory database and a simple query, such as `cargo run --bin tursodb :memory: 'SELECT 1+1;'`. This validates basic execution and instrumentation.
Inconsistent Turso database logs often result from bytecode differences, race conditions, or data corruption. Collect and correlate these logs to reproduce failures in tests and production-like runs for root cause analysis.
bdgscotlandRun Amiga binaries under Vamos and compare output against native builds.
wodehClassify software bugs by pattern and produce a structured debug report.
timequityEnforce a four-phase root-cause investigation workflow before applying fixes to bugs and test failures.
harperaaDetect race conditions and business-logic vulnerabilities in AI-generated code.
