feat(db-browser): install DB Browser for SQLite + open a .sqlite file#1057
Open
liususan091219 wants to merge 1 commit into
Open
feat(db-browser): install DB Browser for SQLite + open a .sqlite file#1057liususan091219 wants to merge 1 commit into
liususan091219 wants to merge 1 commit into
Conversation
New user-invocable skill `skills/db-browser/` — `/db-browser <path>`, macOS only. Installs DB Browser for SQLite via Homebrew if missing (`brew install --cask db-browser-for-sqlite`) and opens the .sqlite file at the given path. Quits any running DB Browser first when switching files so the new file isn't shadowed by the previous open's cached snapshot. Scope is deliberately tight: install + open. No screenshot, no SQL, no schema inspection — anything else is the operator's job in the GUI. Default path when invoked with no argument: $SUTANDO_WORKSPACE/data/ conversation.sqlite (falling back to ~/.sutando/workspace/data/ conversation.sqlite). Works on any .sqlite file when given an explicit path. Used routinely during Sutando operations to inspect the per-surface conversation tables (voice / phone / discord_voice from #1051) without hand-writing SQL. Single SKILL.md, no scripts/ directory needed — install + open is a 2-command flow. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
5 tasks
sonichi
approved these changes
May 23, 2026
Owner
sonichi
left a comment
There was a problem hiding this comment.
LGTM. Already reviewed Lucy's db-browser skill on sonichi/sutando-skills#18 — same content, same scope, clean either home.
Scope is appropriately tight (install + open, no SQL execution or schema inspection). Default path $SUTANDO_WORKSPACE/data/conversation.sqlite matches the workspace_default convention. brew install --cask is the standard install path. Quitting any running DB Browser instance before opening the new file is the right move (cached-snapshot trap is real).
If db-browser is also landing on sonichi/sutando-skills as #18, you'll want to pick one home and close the other to avoid divergence; either repo is fine, just don't carry both.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
New user-invocable skill
skills/db-browser/—/db-browser <path>. macOS only.Installs DB Browser for SQLite via Homebrew if missing (
brew install --cask db-browser-for-sqlite), then opens the.sqlitefile at the given path. Quits any already-running DB Browser instance first when switching files so the new file isn't shadowed by the previous open's cached snapshot.Scope
Deliberately tight: install + open, nothing else. No screenshot capture, no SQL execution, no schema inspection — anything beyond opening is the operator's job in the DB Browser GUI.
Default path
When invoked with no argument, defaults to
$SUTANDO_WORKSPACE/data/conversation.sqlite(falling back to~/.sutando/workspace/data/conversation.sqlitewhen the env var is unset). Works on any.sqlitefile when given an explicit path.Why this lives here
Used routinely during Sutando operations to inspect the per-surface conversation tables (
voice/phone/discord_voicefrom #1051) — and during #1051 development itself for visual verification — without hand-writing SQL each time. Default path baked to the Sutando workspace; not a generic standalone skill.Single-file skill
No
scripts/directory needed — install + open is two commands.Test plan
/db-browserwith no arg + Sutando workspace present → opens~/.sutando/workspace/data/conversation.sqlitein DB Browser; errors gracefully if file absent/db-browser /path/to/foo.sqliteon a fresh machine without DB Browser → triggersbrew install --cask, then opens/db-browser /path/to/foo.sqlitewith DB Browser already open on/other.sqlite→ quits the old, opens the new (no stale snapshot)/db-browser /nonexistent.sqlite→ clean error, no install attempt🤖 Generated with Claude Code