dolt-mcp-vcs

One skill for every make and model of Dolt: detect the flavor and mode first, then do version-control work over the beads (bd) backend and DoltHub.

Formerly beads-dolt — same plugin, renamed to its Dolt-first identity. The beads-dolt install slug still resolves (a deprecated catalog alias) and /beads-dolt is still an accepted trigger, so existing installs keep working — beads is now use-case adapter #1, not the whole skill.

The Dolt and DoltHub-aware layer for the beads (bd) task tracker. It composes with — does not replace — the global beads skill: that skill runs the bead work cycle; this one handles the Dolt backend, DoltHub visibility, and the bd plus Dolt failure modes.

Overview

bd stores every issue in a version-controlled Dolt database. Two things bite teams repeatedly:

"My beads aren't showing in DoltHub." The overwhelmingly common cause is that the workspace's Dolt repo has no remote configured — so nothing is ever pushed. A file-protocol or GitHub backup does not make beads appear on DoltHub; only a Dolt remote plus a push does.
JSONL appears stale after rapid writes. This is the export throttle, not data loss. As of bd 1.0.4 the historical rapid-write race (failure mode 6) is fixed at the SQL-transaction level; the database is always correct, only the issues.jsonl file can lag.

This skill diagnoses both, applies the fixes, and routes deeper work to five bundled agents. It keeps no frozen copy of bd/Dolt internals — a baked snapshot goes stale the moment upstream ships a release; the installed binary wins on any conflict. Verify version-specific behavior live (bd --help, bd <cmd> --help, bd dolt show) and consult the upstream docs; Read references/dolt-internals.md for the directory of those authoritative sources. The agents fetch current truth in their own context, so answers track the installed binary rather than a guess.