Using SQLite Worktrees

Overview

Rails projects on SQLite (especially Rails 8 with Solid Queue/Cache/Cable) keep their development data in storage/*.sqlite3 files. When you create a new git worktree, that directory is empty — so bin/rails console, feature work, or spec runs against real data all fail until you re-migrate and re-seed. This skill copies the main working tree's SQLite files into the new worktree safely, handling WAL journal mode and Rails 8 multi-database layouts.

Core principle: Checkpoint before copy. Copy sidecars with the main file. Back up before overwrite.

Announce at start: "I'm using the using-sqlite-worktrees skill to copy SQLite development databases into the worktree."

When to Activate

Activate in two situations:

1. Delegated from using-git-worktrees — that skill detects a Rails+SQLite project after running bundle install and delegates here before running bin/rails db:test:prepare.
2. Invoked directly — user says something like "copy my SQLite data into the worktree" or "refresh the worktree with current dev data."