1. Habit
  2. Skills
  3. Debugging skill
tursodatabase · 1K installs

Debugging skill
Runs by itself, when someone reports a mismatch.

Each odd result traced to its cause and logged.

Install the Debugging skill and make it a habit: follow https://gethabit.dev/skills/tursodatabase/debugging.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

1K installs25K starsMIT licenceSource on GitHub ↗

Debugging

by tursodatabase · 1K installs

The skill

Shows how to hunt bugs in the Turso database.

Only when you ask.

Faster fixes

Each odd result traced to its cause and logged. Bugs found faster.

↻ Runs by itselfwhen someone reports a mismatch

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

SQLite mismatch reported. Runs in GitHub Actions or Claude Code routine.

  • ↻ SQLite mismatch reported
  • new issue reporting different results than sqlite3

02

It checks its work

bytecode compared, bug reproduced. If a check fails, it tells you.

  • ✓EXPLAIN output captured from sqlite3 and tursodb
  • ✓bug layer named from the bytecode comparison
  • ✓the query reproduces the mismatch with cargo run --bin tursodb
  • ✓make test passes after any fix

03

It remembers

compat triage log. The next run reads it first: mismatches triaged before, their layer and simulator seeds.

loops/turso-compat-triage-loop/log.md

One run, step by step.
Then it stops.

Stop ruleStops after one reported mismatch per run.

  1. 01

    Run in sqlite3

    Your agent runs EXPLAIN on the query with sqlite3 :memory:.

  2. 02

    Run in tursodb

    It runs the same EXPLAIN with cargo run --bin tursodb :memory:.

  3. 03

    Compare bytecode

    Different bytecode points to code generation; same bytecode with different results points to the VM or storage.

  4. 04

    Trace the core

    It reruns tests with RUST_LOG=none,turso_core=trace make test and reads testing/test.log.

  5. 05

    Reproduce with a seed

    For timing bugs it uses limbo_sim with -s <seed> or the concurrent simulator.

  6. 06

    Log the finding

    It records the query, layer, seed and next step in the log.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Debugging skill helps.

Use it when

  • ✓ tursodb results differ from SQLite
  • ✓ a concurrency bug needs a seed
  • ✓ checking stack use of deep expressions

Skip it when

  • – you debug an app that only uses Turso
  • – you work on another database

Questions

Debugging skill, answered.

What about threading bugs?

The skill uses turso_stress under ThreadSanitizer on the nightly toolchain.

What about WAL corruption?

It points to the corruption tools in scripts and references/CORRUPTION-TOOLS.md.

How do I install the Debugging skill?

Copy the prompt at the top into your agent. It installs the skill from tursodatabase/turso and sets up the habit. Or run npx skills add tursodatabase/turso --skill debugging.

Is the Debugging skill free?

Yes. It is published under MIT. Habit is free too.

Debugging. Now as a habit.

Install the Debugging skill and make it a habit: follow https://gethabit.dev/skills/tursodatabase/debugging.md

  • Free
  • No account
  • Undo in one line

All tursodatabase skills →More code skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by tursodatabase, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.